---
title: "Submit registration"
method: POST
path: "/v1/projects/{projectId}/registrations"
tags: ["registrations"]
---

# Submit registration

`POST /v1/projects/{projectId}/registrations`

The endpoint creates a registration with specified policyId and registration's Data. The registration will be validated against the selected policy before submission. After this endpoint gets a 200, the registration will be in IN_QUEUE state, and will be editable. For those registrations that need attachments, they must be provided in a separated endpoint.

## Path parameters

- `projectId` string, required

## Request body

- RegistrationCreateBody
  - `callbackUrl` string — Webhook URL to specify an endpoint for delivery of notifications about registration updates
  - `notificationContacts` string[] — Email addresses that will be notified of any status changes of the registration.
  - `policyId` string — Policy id that applies the registration.
  - `requestDetails` RequestDetails[] — Details of the sender IDs to be registered. Details depend on the specific market requirements defined in the policy.
    - `additionalDetails` object[] — Additional details required for this registration, e.g. company details, contact information or market specific details (only in RCS). Schema and content depend on the specific market requirements defined in the policy Json format is '{key:value, key:value}' with types like string, array, array of objects
    - `senderIdDetails` object[] — Data related to the sender ID values requested in this registration. Schema and content depend on the specific market requirements defined in the policy. Json format is '{key:value, key:value}' with types like string, array, array of objects
  - `tags` string[] — User tags used for the registration. Tag have to start from '#' and contains only alphanumerics and dashes.
  - `servicePlanId` string — Service plan ID or System ID that the registration applies to. When included, the sender id will be configured linked to the service/system plan.

## Response `200`

OK

- GetRegistrationResponse — Registration content
  - `attachments` Attachment[] — Files attached to this registration
    - `attachmentId` string — Unique identifier of the attachment.
    - `createTime` string — Create time of the request. ISO date time format in UTC without timezone offset.
    - `fileName` string — Human readable name of the attachment.
    - `mimeType` string — MIME type of the attachment file.
    - `updateTime` string — Update time of the request. ISO date time format in UTC without timezone offset.
    - `uploadStatus` 'COMPLETED' | 'WAITING' | 'FAILED' — Status of the file uploaded
    - `documentType` string — Type of document attached.
  - `callbackUrl` string — Webhook URL to specify an endpoint for delivery of notifications about registration updates
  - `createTime` string — Creation time of the request. ISO date time format in UTC without timezone offset.
  - `etaDate` string — Expected date of the registration approval. ISO date format.
  - `id` string — Unique registration identifier.
  - `logs` LogEntry[] — Detailed history of the status changes this registration went through
    - `createTime` string — Create time of this log entry. ISO date time format in UTC
    - `message` string — Optional message with details of the registration status update. Can contain information provided by the agent handling the request.
    - `registrationState` string — State of the registration after this entry was created
  - `notificationContacts` string[] — Email addresses that will be notified of any status changes of the registration.
  - `owner` string — Display name of the user that created the registration.
  - `policyId` string — Unique identifier of the policy for this registration.
  - `price` Pricing
    - `currency` string — Currency of the fees
    - `frequency` integer — Recurrent subscription period in month, 0 if no subscription fees
    - `mode` 'SUBSCRIBED' | 'MANUAL' | 'NONE', enum — Type of policy pricing.
    - `recurrentFeeAmount` string — Recurrent subscription fee amount
    - `setupFeeAmount` string — One time setup fee amount
  - `registrationType` 'ALPHANUMERIC_SENDER_ID' | 'LONG_NUMBER' | 'SHORT_CODE' | 'RCS_AGENT', enum — Specify the sender ID type
  - `requestDetails` RequestDetails[] — Details of the sender IDs to be registered. Details depend on the specific market requirements defined in the policy.
    - `additionalDetails` object[] — Additional details required for this registration, e.g. company details, contact information or market specific details (only in RCS). Schema and content depend on the specific market requirements defined in the policy Json format is '{key:value, key:value}' with types like string, array, array of objects
    - `senderIdDetails` object[] — Data related to the sender ID values requested in this registration. Schema and content depend on the specific market requirements defined in the policy. Json format is '{key:value, key:value}' with types like string, array, array of objects
  - `senderIds` string[] — List of sender IDs associated with this registration. If sender IDs are not provided in the request, they will be assigned after registration approval.
  - `status` 'DRAFT' | 'IN_QUEUE' | 'IN_PROGRESS' | 'APPROVED' | 'REJECTED' | 'PENDING' | 'ON_HOLD' | 'PENDING_APPROVAL' | 'PENDING_ATTACHMENTS' — Status of the registration.
  - `tags` string[] — User tags used for the registration. Tag have to start from '#' and contains only alphanumerics and dashes.
  - `updateTime` string — Update time of the request. ISO date time format in UTC without timezone offset.
  - `servicePlanId` string — Service plan ID or System ID that the registration applies to. When included, the sender id will be configured linked to the service/system plan.

## Other responses

- `400` — BAD_REQUEST: Registration validation error
- `404` — NOT_FOUND: Policy not found
- `500` — INTERNAL: Internal server error. Typically, a server bug.

---

[API](https://skmtc.net/sinch/apis/sinch-sender-id-registrations-api.md) · [All operations](https://skmtc.net/sinch/apis/sinch-sender-id-registrations-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/sinch/sinch-sender-id-registrations-api/revisions/e93587db2688/schema)