Skip to main content
POST
Upload certificate

Authorizations

Authorization
string
header
default:App
required

This is the most secure authorization type and the one with the most flexibility.

API keys can be generated by calling the dedicated API method. Furthermore, API keys can have a limited scope and cover only some API methods. Lastly, they can be revoked at any time. This range of possibilities makes API keys well suited for separating the API access rights across multiple applications or use cases. Finally, the loss of an API key is easily manageable.

You can manage your API keys from GUI, or programmatically with dedicated API.

API key Authorization header example:

Body

application/json
certificateId
string
required

Certificate's identifier. Must contain only alphanumeric characters, dots, hyphens, and underscores (pattern: [a-zA-Z0-9._-]). This identifier will be used as part of a URL path. You cannot change the ID once an item is created.

Required string length: 1 - 255
Pattern: ^[a-zA-Z0-9._-]+$
certificateContent
file
required

Content of a .pem file encoded in Base64 format.

Minimum string length: 1
passphrase
file

Certificate's passphrase encoded in Base64 format.

Response

Created.

certificateId
string

Certificate identifier.

status
enum<string>

Certificate status. Represents a certificate state and indicates whether the certificate can be used. PROCESSING means certificate is being synced on Phonovation Platform and cannot be use for notification events. READY means certificate is synced and notification events can be sent to webhook using the certificate. EXPIRED means certificate cannot be used because validity date is in the past.

Available options:
PROCESSING,
READY,
EXPIRED