Create a callback secret | emnify Documentation

Creates a new secret that may be used by API callbacks.

When an api_secret is assigned to a Service Profile with an API callback, API requests towards this URL will contain an Authorization header with a JSON Web Token. The api_secret is used as the Signing Key of the JWT.

Creates a new secret that may be used by API callbacks.

Authentication

AuthorizationBearer

An auth_token should be provided to authenticate a session.

To obtain an auth_token, see the /api/v1/authenticate POST request.

Request

This endpoint expects an object.

organisation_idstringOptional

purposestringOptional

idintegerOptional

Response

Resource Created

An auth_token should be provided to authenticate a session.

To obtain an auth_token, see the /api/v1/authenticate POST request.

This endpoint expects an object.

$	curl -X POST https://cdn.emnify.net/api/v1/api_secret \
>	-H "Authorization: Bearer <token>" \
>	-H "Content-Type: application/json" \
>	-d '{
>	"purpose": "Testing Callback Secret from Swagger",
>	"secret": "P9MM^Y$n83jgx5z"
>	}'

$	curl -X POST https://cdn.emnify.net/api/v1/api_secret \
>	-H "Authorization: Bearer <token>" \
>	-H "Content-Type: application/json" \
>	-d '{
>	"purpose": "Testing Callback Secret from Swagger",
>	"secret": "P9MM^Y$n83jgx5z"
>	}'