About & Auth.

An API to deal with the Flexisip server.

The API is available under /api

A content-type and accept HTTP headers are REQUIRED to use the API properly

> GET /api/{endpoint}
> content-type: application/json
> accept: application/json

Restricted endpoints are protected using a DIGEST authentication or an API Key mechanisms.

Access model

The endpoints are accessible using three different models:

  • Public publicly accessible
  • User the endpoint can only be accessed by an authenticated user
  • Admin the endpoint can be only be accessed by an authenticated admin user

Using the API Key

You can retrieve an API Key from your account panel or using the dedicated API endpoint.

The generated API Key will be restricted to the IP that generates it and will be destroyed if not used after some times.

You can then use your freshly generated key by adding a new x-api-key header to your API requests:

> GET /api/{endpoint}
> x-api-key: {your-api-key}
> …

Or using a cookie:

> GET /api/{endpoint}
> Cookie: x-api-key={your-api-key}
> …

Using a JWT token

You can use a JWT token to authenticate on the API.

To do so you MUST inject it as an Authorization: Bearer header and configure the API with the public key of the token emitter.

> GET /api/{endpoint}
> Authorization: Bearer {your-jwt-token}
> …

The API will then check if the token was signed properly, is still valid and authenticate a user that is actually available in the system.

Using DIGEST

To discover the available hashing algorythm you MUST send an unauthenticated request to one of the restricted endpoints.
Only DIGEST-MD5 and DIGEST-SHA-256 are supported through the authentication layer.

A from (consisting of the user SIP address, prefixed with sip:) header is required to initiate the DIGEST flow.

> GET /api/{restricted-endpoint}
> from: sip:foobar@sip.example.org
> …

< HTTP 401
< content-type: application/json
< www-authenticate: Digest realm=test,qop=auth,algorithm=MD5,nonce="{nonce}",opaque="{opaque}"
< www-authenticate: Digest realm=test,qop=auth,algorithm=SHA-256,nonce="{nonce}",opaque="{opaque}"

You can find more documentation on the related IETF RFC-7616.

Endpoints

Ping

GET /ping

Public

Returns pong

Account Creation Request Tokens

An account_creation_request_token is a unique token that can be validated and then used to generate a valid account_creation_token.

POST /account_creation_request_tokens

Public

Create and return an account_creation_request_token that should then be validated to be used.

Account Creation Tokens

An account_creation_token is a unique token that allow the creation or the validation of a unique account.

POST /account_creation_tokens/send-by-push

Public

Create and send an account_creation_token using a push notification to the device. Return 403 if a token was already sent, or if the tokens limit is reached for this device. Return 503 if the token was not successfully sent.

JSON parameters:

POST /account_creation_tokens/using-account-creation-request-token

Public

Create an account_creation_token using an account_creation_request_token. Return an account_creation_token. Return 404 if the account_creation_request_token provided is not valid or expired otherwise.

JSON parameters:

POST /account_creation_tokens

Admin

Create and return an account_creation_token.

Auth Tokens

POST /accounts/auth_token

Public

Generate an auth_token. To attach the generated token to an account see auth_token attachement endpoint.

Return the auth_token object.

GET /accounts/auth_token/{auth_token}/attach

User

Attach a publicly generated authentication token to the currently authenticated account.

Return 404 if the token is non existing or invalid.

Accounts

POST /accounts/public

Deprecated Public Unsecure endpoint

Create an account. Return 422 if the parameters are invalid. Send an email with the activation key if email is set, send an SMS otherwise.

JSON parameters:

POST /accounts/with-account-creation-token

Public

Create an account using an account_creation_token. Return 422 if the parameters are invalid or if the token is expired.

JSON parameters:

GET /accounts/{sip}/info

Public

Retrieve public information about the account. Return 404 if the account doesn't exists.

GET /accounts/{phone}/info-by-phone

Deprecated Public Unsecure endpoint

Retrieve public information about the account. Return 404 if the account doesn't exists.

Return phone: true if the returned account has a phone number.

POST /accounts/recover-by-phone

Deprecated Public Unsecure endpoint

Send a SMS with a recovery PIN code to the phone number provided. Return 404 if the account doesn't exists.

Can only be used once, a new recover_key need to be requested to be called again.

JSON parameters:

GET /accounts/{sip}/recover/{recover_key}

Deprecated Public Unsecure endpoint

Activate the account if the correct recover_key is provided.

The sip parameter can be the default SIP account or the phone based one.

Return the account information (including the hashed password) if valid.

Return 404 if the account doesn't exists.

POST /accounts/{sip}/activate/email

Deprecated Public

Use POST /accounts/me/email/request instead.

Activate an account using a secret code received by email. Return 404 if the account doesn't exists or if the code is incorrect, the validated account otherwise.

JSON parameters:

POST /accounts/{sip}/activate/phone

Deprecated Public

Use POST /accounts/me/phone/request instead.

Activate an account using a pin code received by phone. Return 404 if the account doesn't exists or if the code is incorrect, the validated account otherwise.

JSON parameters:

GET /accounts/me/api_key/{auth_token}

Public

Generate and retrieve a fresh API Key from an auth_token. The auth_token must be attached to an existing account, see auth_token attachement endpoint to do so.

Return 404 if the token is invalid or not attached.

This endpoint is also setting the API Key as a Cookie.

GET /accounts/me/api_key

User

Generate and retrieve a fresh API Key. This endpoint is also setting the API Key as a Cookie.

GET /accounts/me

User

Retrieve the account information.

GET /accounts/me/provision

User

Provision the account by generating a fresh provisioning_token.

Return the account object.

DELETE /accounts/me

User

Delete the account.

POST /accounts/me/password

User

Change the account password.

JSON parameters:

POST /accounts

Admin

To create an account directly from the API. Deprecated If activated is set to false a random generated confirmation_key and provisioning_token will be returned to allow further activation using the public endpoints and provision the account. Check confirmation_key_expires to also set an expiration date on that confirmation_key.

JSON parameters:

PUT /accounts/{id}

Admin

Update an existing account. Ensure to resend all the parameters to not reset them.

JSON parameters:

GET /accounts

Admin

Retrieve all the accounts, paginated.

GET /accounts/{id}

Admin

Retrieve a specific account.

GET /accounts/{sip}/search

Admin

Search for a specific account by sip address.

GET /accounts/{email}/search-by-email

Admin

Search for a specific account by email.

DELETE /accounts/{id}

Admin

Delete a specific account and its related information.

POST /accounts/{id}/activate

Admin

Activate an account.

POST /accounts/{id}/deactivate

Admin

Deactivate an account.

POST /accounts/{id}/block

Admin

Block an account.

POST /accounts/{id}/unblock

Admin

Unblock an account.

GET /accounts/{id}/provision

Admin

Provision an account by generating a fresh provisioning_token.

Accounts email

POST /accounts/me/email/request

User

Change the account email. An email will be sent to the new email address to confirm the operation.

JSON parameters:

Accounts phone number

POST /accounts/me/phone/request

User

Request a specific code by SMS.

Will return 403 if the account doesn't have a validated Account Creation Token attached to it.

JSON parameters:

POST /accounts/me/phone

User

Confirm the code received and change the phone number. Activate the account.

JSON parameters:

Return the updated account.

Accounts devices

GET /accounts/me/devices

User

Return the user registered devices.

DELETE /accounts/me/devices/{uuid}

User

Remove one of the user registered devices.

Account contacts

GET /accounts/me/contacts

User

Return the user contacts.

GET /accounts/me/contacts/{sip}

User

Return a user contact.

Contacts

GET /accounts/{id}/contacts

Admin

Get all the account contacts.

POST /accounts/{id}/contacts/{contact_id}

Admin

Add a contact to the list.

DELETE /accounts/{id}/contacts/{contact_id}

Admin

Remove a contact from the list.

Dictionary

GET /accounts/{id}/dictionary

Admin

Get all the account dictionary entries.

POST /accounts/{id}/dictionary/{key}

Admin

Add or update a new entry to the dictionary

JSON parameters:

DELETE /accounts/{id}/dictionary/{key}

Admin

Remove an entry from the dictionary.

Account Actions

The following endpoints will return 403 Forbidden if the requested account doesn't have a DTMF protocol configured.

GET /accounts/{id}/actions

Admin

Show an account related actions.

GET /accounts/{id}/actions/{action_id}

Admin

Show an account related action.

POST /accounts/{id}/actions/

Admin

Create an account action.

JSON parameters:

PUT /accounts/{id}/actions/{action_id}

Admin

Create an account action.

JSON parameters:

DELETE /accounts/{id}/actions/{action_id}

Admin

Delete an account related action.

Contacts Lists

GET /contacts_lists

Admin

Show all the contacts lists.

GET /contacts_lists/{id}

Admin

Show a contacts list.

POST /contacts_lists

Admin

Create a contacts list.

JSON parameters:

PUT /contacts_lists/{id}

Admin

Update a contacts list.

JSON parameters:

DELETE /contacts_lists/{id}

Admin

Delete a contacts list.

POST /contacts_lists/{contacts_list_id}/contacts/{contact_id}

Admin

Add a contact to the contacts list.

DELETE /contacts_lists/{contacts_list_id}/contacts/{contact_id}

Admin

Remove a contact from the contacts list.

POST /accounts/{id}/contacts_lists/{contacts_list_id}

Admin

Add a contacts list to the account.

DELETE /accounts/{id}/contacts_lists/{contacts_list_id}

Admin

Remove a contacts list from the account.

Account Types

GET /account_types

Admin

Show all the account types.

GET /account_types/{id}

Admin

Show an account type.

POST /account_types

Admin

Create an account type.

JSON parameters:

PUT /account_types/{id}

Admin

Update an account type.

JSON parameters:

DELETE /account_types/{id}

Admin

Delete an account type.

POST /accounts/{id}/types/{type_id}

Admin

Add a type to the account.

DELETE /accounts/{id}/contacts/{type_id}

Admin

Remove a type from the account.

Messages

POST /messages

Admin

Send a message over SIP.

JSON parameters:

Statistics

FlexiAPI can record logs generated by the FlexiSIP server and compile them into statistics.

POST /statistics/messages

Admin

Announce the creation of a message.

JSON parameters:

PATCH /statistics/messages/{message_id}/to/{to}/devices/{device_id}

Admin

Complete a message status.

JSON parameters:

POST /statistics/calls

Admin

Announce the beginning of a call.

JSON parameters:

PATCH /statistics/calls/{call_id}/devices/{device_id}

Admin

Complete a call status.

JSON parameters:

PATCH /statistics/calls/{call_id}

Admin

Update a call when ending.

JSON parameters:

Non-API Endpoints

The following URLs are not API endpoints they are not returning JSON content and they are not located under /api but directly under the root path.

Contacts list

GET /contacts/vcard

User

Return the authenticated user contacts list, in vCard 4.0 format.

Here is the format of the vCard list returned by the endpoint:

BEGIN:VCARD
VERSION:4.0
KIND:individual
IMPP:sip:schoen.tatyana@sip.linphone.org
FN:schoen.tatyana@sip.linphone.org
X-LINPHONE-ACCOUNT-DTMF-PROTOCOL:sipinfo
X-LINPHONE-ACCOUNT-TYPE:phone
X-LINPHONE-ACCOUNT-ACTION:action_key;123
END:VCARD
BEGIN:VCARD
VERSION:4.0
KIND:individual
IMPP:sip:dhand@sip.linphone.org
FN:dhand@sip.linphone.org
X-LINPHONE-ACCOUNT-DTMF-PROTOCOL:sipinfo
END:VCARD

GET /contacts/vcard/{sip}

User

Return a specific user authenticated contact, in vCard 4.0 format.