@@ -4897,13 +4897,6 @@ paths:
48974897 clients to connect to.
48984898
48994899
4900- Before calling this endpoint, a configuration for the partner must exist.
4901-
4902- If a config is not present for the partner, the request will fail with a 422 error.
4903-
4904- To initiate the creation of a partner config, please reach out to the
4905- Go Network Engineering team at:
[email protected] .
4906-
49074900 Error scenarios:
49084901 - 400: Invalid Request Error
49094902 - Occurs when the request parameters are invalid or incomplete.
@@ -4917,10 +4910,6 @@ paths:
49174910 - Occurs when the authenticated partner doesn't have access to create a partner.
49184911 - Examples: Enterprise does not have OES license.
49194912
4920- - 422: Unprocessable Entity Error
4921- - Returned when a required partner configuration is missing.
4922- - Examples: Partner configuration is missing.
4923-
49244913 - 500: Internal Server Error
49254914 - Occurs when there's an unexpected error processing the request
49264915 - Examples: Database connection failure, transient network error.
@@ -4996,12 +4985,6 @@ paths:
49964985 application/json:
49974986 schema:
49984987 $ref: '#/components/schemas/V1ErrorPayload'
4999- '422':
5000- description: Unprocessable Entity
5001- content:
5002- application/json:
5003- schema:
5004- $ref: '#/components/schemas/V1ErrorPayload'
50054988 '500':
50064989 description: Internal Server Error
50074990 content:
0 commit comments