You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The getAccount endpoint in the OpenAPI spec is incorrectly documented as returning an array of accounts, but it actually returns a single account object.
The endpoint should be documented as returning a single Account object, not an array.
Context
This discrepancy was identified during development work where the actual API response returns a single account object, but the generated types and documentation suggest it returns an array. This causes confusion for developers using the API and can lead to incorrect implementation.
Solution
Update the OpenAPI specification to correctly reflect that the getAccount endpoint returns a single account object rather than an array of accounts.
Related
Similar issue was previously fixed for getCurrentUser in #557.
The text was updated successfully, but these errors were encountered:
CalebBarnes
changed the title
Fix getAccount endpoint response type from array to single account object
Fix getAccount endpoint response type from array to single account object
Jun 10, 2025
The getAccount endpoint was incorrectly documented as returning an array
of accountMembership objects, but it actually returns a single
accountMembership object. This change updates the OpenAPI specification
to correctly reflect the actual API behavior.
This fix ensures consistency with other similar single-object endpoints
like createAccount, updateAccount, and getCurrentUser.
Fixes#567
Issue Description
The
getAccount
endpoint in the OpenAPI spec is incorrectly documented as returning an array of accounts, but it actually returns a single account object.Current Behavior
The OpenAPI spec shows:
Reference: https://open-api.netlify.com/#tag/accountMembership/operation/getAccount
Expected Behavior
The endpoint should be documented as returning a single
Account
object, not an array.Context
This discrepancy was identified during development work where the actual API response returns a single account object, but the generated types and documentation suggest it returns an array. This causes confusion for developers using the API and can lead to incorrect implementation.
Solution
Update the OpenAPI specification to correctly reflect that the
getAccount
endpoint returns a single account object rather than an array of accounts.Related
Similar issue was previously fixed for
getCurrentUser
in #557.The text was updated successfully, but these errors were encountered: