How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Kudosity Senders API

The Senders API from Kudosity — 4 operation(s) for senders.

Kudosity Senders API is one of 12 APIs that Kudosity publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Senders. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 5 operations across 4 paths, and defines 30 schemas. It is described by OpenAPI 3.2.0, at version 20250101.

Requests are made against a single base URL, https://api.transmitmessage.com.

5 operations 4 paths 30 schemas 1 DELETE1 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
20250101
Base URL
https://api.transmitmessage.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Kudosity Senders API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). By default, every request must be authenticated.

  • ApiKeyAuth — All API requests require your API credentials, you will find them once logged into your account on the SETTINGS page. Scroll down to API Settings to find your…

Paths & Operations 5

Across 4 paths, the API surfaces 5 operations — 1 DELETE, 1 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Senders 5
GET
/v2/senders/registrations
List sender registrations
5 params → 200400401500
POST
/v2/senders/registrations
Create a sender registration
body → 201400401409429500
DELETE
/v2/senders/phone-numbers/{phone_number}
Delete a sender by phone number
2 params → 204400401404500
POST
/v2/senders/registrations/{registration_id}/verifications
Request a verification code
1 param body → 201400401404409500
POST
/v2/senders/registrations/{registration_id}/verifications/confirmation
Confirm a verification code
1 param body → 200400401404409429500

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are SenderRegistration (9 properties), Verification (6 properties), VerificationConfirmationInputValidationProblem (6 properties), PagePaginationMeta (4 properties). Each schema is shown below with its type and property counts.

SenderRegistrationStatus
string
Status of a sender registration. The same coarse set of statuses applies to every registration type: - PERSONALMOBILENUMBER — PENDINGAPPROVAL, VERIFIED, REJECT…
CommonErrorResponse
VerificationStatus
string
Status of a sender registration verification.
ProblemDetails
object
A Problem Details object (RFC 9457). Additional properties specific to the problem type may be present.
4 properties 4 required
Uri
string
string providing an URI formatted according to IETF RFC 3986.
SenderRegistrationDetails
object
Type-specific details for a sender registration. The populated sub-object matches the registration type — for an ALPHANUMERIC registration, alphanumeric is pre…
1 property
SenderRegistration
object
A sender registration record.
9 properties 7 required
VerificationConfirmationInputValidationProblem
object
Input-validation problem (RFC 9457) specific to the verification confirmation endpoint. Extends the standard InputValidationProblem with a structured attemptsr…
6 properties 5 required
SenderRegistrationRequest
object
Request body for creating a sender registration.
4 properties 3 required
TooManyRequestsProblem
object
HTTP 429 Too Many Requests - Rate limit exceeded. Your client application has sent too many requests in a given amount of time and should retry later.
AlphanumericDetails
object
Details specific to an alphanumeric (alpha) sender registration.
3 properties 1 required
VerificationConfirmation
object
The result of a successful verification code confirmation.
3 properties 3 required
AlphanumericStatus
string
Fine-grained registry lifecycle status for an alphanumeric registration — the state the customer sees on screen, distinct from the coarse root status. This enu…
SenderRegistrationRequestType
string
Type of sender registration that can be created through the public API. Only PERSONALMOBILENUMBER is supported here; alpha (ALPHANUMERIC) registrations are cre…
Registry
string
The registry body an alphanumeric sender registration is submitted to. - ACMA — Australian Communications and Media Authority.
InternalServerErrorProblem
object
This problem occurs when the server encounters an unexpected condition that prevents it from fulfilling the request. Your client application did everything cor…
SenderRegistrationType
string
Type of a sender registration record (as returned by the API). - PERSONALMOBILENUMBER — a personal mobile number registered as a sender. - ALPHANUMERIC — an al…
InputValidationProblem
object
This problem occurs when the request is deemed unprocessable. Your client issued a request that failed validation. Certain validation libraries return multi-er…
InputValidationIssue
object
An issue detected during input validation.
3 properties
PagePaginationMeta
object
Pagination metadata for page-based pagination. Reusable across all paginated API endpoints that use page/limit pagination.
4 properties 4 required
Verification
object
A verification record for a sender registration.
6 properties 6 required
VerificationRequest
object
Request body for requesting a verification code.
2 properties 2 required
CommonResponseMeta
object
2 properties
VerificationConfirmRequest
object
Request body for confirming a verification code.
1 property 1 required
UnauthorizedProblem
object
HTTP 401 Unauthorized - API authentication failed. The request was rejected because the API key is missing, invalid, expired, or lacks sufficient permissions f…
ConflictProblem
object
HTTP 409 Conflict - The request conflicts with the current state of the resource. Your client application attempted an operation that conflicts with an existin…
VerificationMethod
string
Method used to deliver the verification code.
NotFoundProblem
object
This problem occurs when the requested resource could not be found. Your client application tried to access a resource that does not exist (or could not be fou…
ListSenderRegistrationsResponse
object
Paginated list of sender registrations.
1 property 1 required
CommonSuccessResponse

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kudosity-senders-api-openapi.yml Raw ↑

Other APIs Kudosity publishes across the network.

Kudosity Account API
Kudosity Contacts & Lists API
Kudosity Email SMS API
Kudosity Keywords API
Kudosity MMS API
Kudosity Numbers API
Kudosity RCS API
Kudosity Reporting API
Kudosity SMS API
Kudosity Webhook API
Kudosity Whats App API
Where this information came from

This is an independent, third-party profile of Kudosity Senders API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.