Connect to partner
Connect your OES client account to an OES partner account, enabling you to trade funds that you have custodied with BitGo. You must have an account on the partner's site. Clients can have multiple connections to the same partner.
Error scenarios:
-
400: Invalid Request Error
-
Occurs when the request parameters are invalid or malformed.
-
Examples: Invalid UUID format for enterpriseId or partnerId, missing required fields, invalid payload format, invalid signature, payload doesn't match request data.
-
401: Authentication Error
-
Occurs when the request is not authorized.
-
Examples: Caller is not a member of the enterprise. Payload/Signature are not valid.
-
403: Permission Denied Error
-
Occurs when the authenticated client doesn't have necessary permissions.
-
Examples: Enterprise does not have OES license.
-
404: Not Found Error
-
Occurs when the specified resources cannot be found.
-
Examples: Enterprise ID doesn't exist, specified partner ID doesn't exist.
-
422: Unprocessable Content Error
-
Occurs when the request is valid but cannot be processed due to business rules.
-
Examples: Invalid connection key schema for partner, unsupported key schema, partner is inactive, client and partner belong to different trust organizations.
-
500: Internal Server Error
-
Occurs when there's an unexpected server error processing the request.
-
Examples: Database connection issues. Transient network errors,
Requires access token scopes: settlement_network_read, settlement_network_write
Path Params
-
enterpriseIdstring required
Body Params
object
-
partnerIdstring required -
namestring required -
connectionKeyobject requiredONE OF
-
schemastring enum requiredtoken -
connectionTokenstring required
-
schemastring enum requiredtokenAndSignature -
connectionTokenstring required -
signaturestring required
-
schemastring enum requiredapiKeyAndSecret -
apiKeystring required -
apiSecretstring required
-
schemastring enum requiredclearloop -
apiKeystring required -
apiSecretstring required -
clientAccountIdstring required -
companyRegistrationNumberstring required
-
-
noncestring required -
payloadstring required -
signaturestring required
Responses
200
OK
Response Body
object
-
connectionobject requiredThe connection details. Contains all information about a specific client-partner connection.connection object
-
idstring requiredThe unique identifier of the connection. This UUID uniquely identifies the connection between a client and partner. -
namestring requiredA user-friendly name for the connection. This is a descriptive label provided by the client for this particular connection. -
clientIdstring requiredThe unique identifier of the client associated with this connection. This UUID uniquely identifies the client organization within the BitGo system. -
partnerIdstring requiredThe unique identifier of the partner associated with this connection. This UUID uniquely identifies the partner organization within the BitGo system. -
networkAccountIdstring requiredThe unique identifier of the network account associated with this connection. This references the account where allocated funds are held for this connection. -
createdAtstring date-time requiredThe date and time when the connection was created. Represented as an ISO 8601 formatted date string. -
updatedAtstring date-time requiredThe date and time when the connection was last updated. Represented as an ISO 8601 formatted date string. -
activeboolean requiredIndicates whether the connection is active. When false, the connection is deactivated and no operations (like allocations) can be performed on it. When true, the connection is active and operations can be performed on it. -
proofstring requiredThe cryptographic proof associated with the connection. This is used for verifying the authenticity of the connection. Derived from the payload and signature submitted when the connection was created. -
noncestring requiredA nonce value used in the connection cryptographic operations. This provides additional security for connection operations. -
evaluationIdstringThe unique identifier of the policy evaluation for this connection. -
pendingApprovalIdstringThe unique identifier of the pending approval for this connection. -
policyResultstring enumThe result of the policy evaluation for this connection.
- 'approved': Policy evaluation passed and the operation was allowed
- 'rejected': Policy evaluation failed and the operation was denied Not present if no policy evaluation was performed or if evaluation is still pending.
approvedrejected -
partnersConnectionIdstring nullable requiredThe partner's identifier for this connection. This is the identifier used by the partner in their system to refer to this connection. Will be null if the connection hasn't been initialized by the partner. -
partnersClientIdstring nullable requiredThe partner's identifier for the client. This is the identifier used by the partner in their system to refer to the client. Will be null if the connection hasn't been initialized by the partner. -
initializedboolean requiredIndicates whether the connection has been initialized by the partner. When true, the partner has established this connection on their side. When false, the connection is pending initialization by the partner.
-
401
Unauthorized
Response Body
object
-
errorstring required
403
Forbidden
Response Body
object
-
errorstring required
404
Not Found
Response Body
object
-
errorstring required
422
Unprocessable Entity
Response Body
object
-
errorstring required
500
Internal Server Error
Response Body
object
-
errorstring required