POST /service/payments/link/:linkId/notifications

Creates link notification

Creates new pay-by-link notification for specified link id

Path Parameters

linkId string required

application/json

Request Body

channel LinkNotificationChannel

Possible values: [email, sms]

target string

Responses

• 200
• 401
• 404

---

pay-by-link notification created successfully

application/json

Schema

Example (from schema)

---

Schema

id LinkNotificationId
channel LinkNotificationChannel

Possible values: [email, sms]

target string
created date-time

RFC 3339 date time format (2007-11-06T16:34:41.000Z)

updated date-time

RFC 3339 date time format (2007-11-06T16:34:41.000Z)

status LinkNotificationStatus

Possible values: [accepted, sent, delivered, error]

status_message string

{
  "id": "string",
  "channel": "email",
  "target": "string",
  "created": "2026-04-17T12:30:51.959Z",
  "updated": "2026-04-17T12:30:51.959Z",
  "status": "accepted",
  "status_message": "string"
}

Unauthorized

application/json

Schema

Example (from schema)

Example

---

Schema

errorMessage string required

Description of error

errorCode ErrorCode required

Possible values: [invalid_parameter, unauthorized, forbidden, not_found, not_allowed, not_acceptable, bad_request, other]

Error code of a specific error. For more details visit https://documentation.fliqa.io/api/errors/{errorCode}

errorSubCode ErrorSubCode

Possible values: [api_key_secret_header_must_be_provided, authorization_header_must_be_provided, access_not_allowed, domain_not_allowed, access_token_expired, invalid_access_scope, invalid_access_environment, invalid_argument, invalid_meta_data, phone_number_invalid, email_invalid, email_or_phone_number_required, invalid_pin, unspecified]

Error sub code of a specific error. For more details visit https://documentation.fliqa.io/api/errors/{errorCode}#{errorSubCode}

documentationUrl uri

Link to documentation if available, typically https://documentation.fliqa.io/api/errors/{errorCode}

requestId RequestId

Unique request id

resourceId ResourceId

Unique resource id

{
  "errorMessage": "string",
  "errorCode": "unauthorized",
  "errorSubCode": "phone_or_email_not_registered",
  "documentationUrl": "string",
  "requestId": "554099e7d0b648d7b96bc31c148425b8",
  "resourceId": "9c14c6f2f0ee4a54a280be3c18ec1dba"
}

{
  "errorCode": "unauthorized",
  "errorMessage": "Not authorized",
  "documentationUrl": "https://documentation.fliqa.io/api/errors/unauthorized"
}

Point of sale not found

application/json

Schema

Example (from schema)

Example

---

Schema

errorMessage string required

Description of error

errorCode ErrorCode required

Possible values: [invalid_parameter, unauthorized, forbidden, not_found, not_allowed, not_acceptable, bad_request, other]

Error code of a specific error. For more details visit https://documentation.fliqa.io/api/errors/{errorCode}

errorSubCode ErrorSubCode

Possible values: [api_key_secret_header_must_be_provided, authorization_header_must_be_provided, access_not_allowed, domain_not_allowed, access_token_expired, invalid_access_scope, invalid_access_environment, invalid_argument, invalid_meta_data, phone_number_invalid, email_invalid, email_or_phone_number_required, invalid_pin, unspecified]

Error sub code of a specific error. For more details visit https://documentation.fliqa.io/api/errors/{errorCode}#{errorSubCode}

documentationUrl uri

Link to documentation if available, typically https://documentation.fliqa.io/api/errors/{errorCode}

requestId RequestId

Unique request id

resourceId ResourceId

Unique resource id

{
  "errorMessage": "string",
  "errorCode": "unauthorized",
  "errorSubCode": "phone_or_email_not_registered",
  "documentationUrl": "string",
  "requestId": "554099e7d0b648d7b96bc31c148425b8",
  "resourceId": "9c14c6f2f0ee4a54a280be3c18ec1dba"
}

{
  "errorCode": "not_found",
  "errorMessage": "Can't find point of sale 'link_id'",
  "documentationUrl": "https://documentation.fliqa.io/api/errors/not_found"
}

Loading...