The Spanish version is the authoritative reference. View in Spanish
ONESOURCE Onboarding APIs
https://gosocket-onboarding-api-sbx.gosocket.nethttps://global-apim-prd.gosocket.net/ms-onboardingapiPartner credentials
To consume any onboarding endpoint you need the TR Partner credentials. They are generated only once for Chile and reused across all countries.
| Field | Description |
|---|---|
partnerId | Unique partner identifier (GUID) |
apiKeyUser | Partner ApiKey for authentication (GUID) |
Request the credentials from the Gosocket support team. They must not be stored in source code or shared over insecure channels. There is a single set per environment (SBX and PRD).
Available methods
createTokenPOSTGenerates the OAuth 2.0 token required to consume the rest of the APIs.createAccountPOSTCreates a company account (asynchronous — returns trackId).getProcessGETQueries the status of the asynchronous process started by createAccount.updateAccountPATCHUpdates the data of an existing account.getAccountGETRetrieves the complete data of a specific account.getAccountsGETLists all accounts associated with the authenticated Partner.blockUnblockCompanyPATCHBlocks or unblocks a company's access to the platform.enableDisableApiKeyPATCHEnables or disables a specific ApiKey for a customer account.getApiKeysGETLists the ApiKeys generated for a customer account.getCertificatesGETLists the certificates loaded for an account.updateCertificateTagPUTUpdates the identification tag of a certificate.deleteCertificateDELETEDeletes a certificate from an account.For all endpoints that require {countryId} in the path, use the ISO country code (e.g.: cl, ar, mx). createToken always uses /cl regardless of the country. Certificate endpoints only apply to countries that require a digital certificate — see Country Parameters.
All endpoints (except createToken) return the same result envelope — value, status, isSuccess, errors[], validationErrors[] — confirmed by the API's Swagger. The "Response — Error" examples on each method page show this real shape; the specific text in errors/validationErrors is illustrative (not taken from a captured response) and may vary by case.
An invalid or expired Bearer token does not go through this envelope: the API responds with HTTP 401 directly, before reaching the method.