Skip to main content

Security

Authentication

To access the API you need a JSON Web Token (JWT), issued in exchange for the ClientId and ClientSecret provided to you. Please ensure that you store these credentials securely.

Every other endpoint in this documentation requires the token in the Authorization header, in the format Authorization: Bearer {token}. The token endpoint itself does not require an Authorization header.

HTTP Request [POST]
https://parceiros.empregos.com.br/oauth/v2/accessToken

The body must be sent as application/x-www-form-urlencoded (not JSON).

curl -X 'POST' \
'https://parceiros.empregos.com.br/oauth/v2/accessToken' \
-H 'accept: */*' \
-H 'Content-Type: application/x-www-form-urlencoded' \
-d 'ClientId={{ClientId}}&ClientSecret={{ClientSecret}}'

Parameters [Request]

FieldDescriptionTypeRequired
ClientIdClient identifier provided to the partner.StringYes
ClientSecretClient secret provided to the partner. It is a GUID, e.g. 3fa85f64-5717-4562-b3fc-2c963f66afa6.GUIDYes

Responses

  • 200 OK: credentials accepted. The response is a JSON object with the issued token in the token property. Send it on every other request as Authorization: Bearer {token}.

  • 400 Bad Request: invalid credentials or an unexpected error.

    {
    "success": false,
    "message": ["Invalidated credentials"]
    }

    If ClientSecret is not a valid GUID, the request is rejected before reaching the credential check, with a standard 400 validation response.

Transport

All endpoints must furnish a verifiable SSL certificate signed by a well-known Certificate Authority (such as those trusted by Mozilla). If your web browser can visit the endpoint without generating a security warning, we can support it.