INinfobip
platform
2fa
pin-sending-and-verification
send-pin-over-voice

Resend 2FA PIN code over Voice

If needed, you can resend the same (previously sent) PIN code over Voice.

post/2fa/2/pin/{pinId}/resend/voice

Request

  • Base URL
    https://api.infobip.com (the document declares no server; this is the origin it was published from)
  • Auth
    • HTTP basic
    • or API key in header Authorization
    • or API key in header Authorization
    • or OAuth 2
      Client credentials
      Token URL: https://api.infobip.com/auth/1/oauth2/token

Path parameters

pinIdstring required

ID of the pin code that has to be verified.

Request body

placeholdersobject

Key value pairs that will be replaced during message sending. Placeholder keys should NOT contain curly brackets and should NOT contain a pin placeholder. Valid example: "placeholders":{"firstName":"John"}

trackDeliveryboolean

Enables sending of delivery reports via Subscriptions. The retry cycle for when your URL becomes unavailable uses the following formula: 1min + (1min * retryNumber * retryNumber).

Response

successful response

callStatusstring

Call status, e.g. PENDING_ACCEPTED.

externalMessageIdstring

Message ID used for delivery tracking.

ncStatusstring

Status of sent Number Lookup. Number Lookup status can have one of the following values: NC_DESTINATION_UNKNOWN, NC_DESTINATION_REACHABLE, NC_DESTINATION_NOT_REACHABLE, NC_NOT_CONFIGURED. Contact your Account Manager, if you get the NC_NOT_CONFIGURED status. SMS will not be sent only if Number Lookup status is NC_NOT_REACHABLE.

pinIdstring

Sent PIN code ID.

smsStatusstring

Sent SMS status. Can have one of the following values: MESSAGE_SENT, MESSAGE_NOT_SENT.

tostring

Phone number to which the 2FA message will be sent. Example: 41793026727.

Changes

No recorded changes to this operation across all 1 revision of this API.