Send Message - Field Descriptions
The following tables describe the fields that you can include in the request and the response for the Send Message endpoint.
Request
The following table describes the fields that you can include in the request.
| Field | Description | Type | Min Length | Max Length | Mandatory |
|---|---|---|---|---|---|
| wsid | The web service ID. This must be unique for every request sent. You can set your own wsid, for example by using the current date and time (20250213145006), or you can leave the field blank and Thredd generates the wsid for you. | N | 0 | 19 | No |
| IssCode | Thredd Issuer (Program Manager) Code. Assigned by Thredd. | AN | 1 | 4 | Yes |
| PAN | Card Number. Required in request if PublicToken is not present. | AN | 14 | 19 | Conditional |
| PublicToken | The card’s public token. Mandatory in request if PAN is not present. | AN | 1 | 9 | Conditional |
| EventId | ID of the event. See Event ID. Thredd generates and sends the appropriate SMS or Email message. | N | 1 | 4 | Yes |
| MailOrSMS | The cardholder's preferred contact method.0 = SMS 1 = email 2 = SMS and emailDefault value is ‘0’. | N | 1 | 1 | Yes |
Response
The following table describes the fields that are included in the response.
| Field | Description |
|---|---|
| IssCode | Thredd Issuer (Program Manager) Code. Assigned by Thredd. |
| PublicToken | The card’s public token. Mandatory in the response. |
| SysDate | The system processing date. |
| ActionCode | The action code for the response. |