Table of Contents | ||
---|---|---|
|
Introduction
With our API it is possible to create PayLinks, e-Mandates and import records for our scripts. To use the PayLink and e-Mandate service, additional configuration and setup are required. Please contact our customer support if you would like to use additional services.
GraphQL
Our API is written in GraphQL. On How To GraphQL you can read the fundamentals. Creating PayLinks should be as easy as using REST an API. We have added some examples on how to use our API with a GraphQL Client.
To explore our API and its documentation you could use the Altair GraphQL Client. This client has the option to set the required authentication header. Watch this demo video to view how to use the built-in documentation browser.
API endpoint
Code Block |
---|
https://reminders.alphacommapi.com/v1 |
Test endpoint
Contact us for the test endpoint and credentials.
API Keys
You will need an access key to connect to our API. Your keys can be managed through our portal. At the portal go to "Account → API keys". You will need to be a portal manager for your company to access this page.
Key usage
For each request set the "X-AUTH-TOKEN"
HTTP header with your key.
Key IP restriction
It is possible to allow keys to only work form certain IP addresses.
Code Block |
---|
127.1.1.1
192.1.0.0/32 |
Code example
We created one request example in PHP to get you started.
APIs
Through our API we provide multiple services. The requirements for fields are defined in the API itself. Use a GraphQL client to view the documentation. In this document we will give you some examples to get started.
All the dates fields in our responses are formatted in RFC 3339, 'Y-m-d\TH:i:sP'.
Import
The import API is an alternative for our batch SFTP (CSV) import. Through this endpoint you are able to import records. The records are batched by day of import and visible in the portal at the import page.
The reminder results are reported at the end of the day in one or multiple result files, grouped by script. For more information see our Annabel Platform Dataformat document.
Required fields
The scripts that are setup in our portal may be setup for voice messages, text messages or emails, that optionally contain a PayLink or e-Mandate. Each script has his own set of required fields.
When a new script is setup we will provide a list of required fields.
Status codes
More information about status codes, these are used at the portal and API.
Batch statuses
Record statuses
Input options
Through the 'addRecords' mutation you are able to add records.
Argument
Description
When to use
rows [RowInput!]
An endpoint that has a preset of fields.
This is the preferred way to deliver your records and usable in most cases.
Use this option for small batches or loose records.
file [FileInput!]
Base64 encoded file.
For example: csv, xml, xlsx, xls, ods.
For large batch import, 1000 or more.
Or when your script requires fields that are not available at the RowInput.
If you have questions please contact us.
Examples
When we setup a new script we will inform you about the required fields.
Row Input
This an example for a mail with PayLink record using the RowInput.
Query
Code Block |
---|
mutation addRecords (
$file: FileInput,
$rows: [RowInput!]
) {
import {
addRecords(file: $file, rows: $rows) {
name
action
status
records {
scriptId
status
messages {
context
message
level
}
}
}
}
} |
Variables
Code Block |
---|
{
"rows": [
{
"reference": "f0e7a0c3",
"script": "1001",
"personFamilyName": "Alphacomm",
"toMailAddress": "reminders@alphacomm.nl",
"invoiceDescription": "Example payment",
"invoiceDate": "2019-04-04",
"invoiceDueDate": "2019-07-30",
"invoiceReference": "40824524",
"invoiceCurrency": "EUR",
"invoiceAmount": "56445",
"invoiceNumber": "249075245",
"personBirthDay": "2000-01-01"
}
]
} |
Response
Code Block |
---|
{
"data": {
"import": {
"addRecords": {
"name": "20190403-965",
"action": "IMPORT",
"status": "done",
"records": [
{
"scriptId": "1001",
"status": "accepted",
"messages": []
}
]
}
}
}
} |
File Input
This is an example with FileInput. Your file should be send as Base64 encoded string. An imported file will always response with a status queued, The slight delay is deliberate, because we need time to process all records. It's possible to send a second request to get the status of the batch.
Query
Code Block |
---|
mutation addFile (
$file: FileInput,
$rows: [RowInput!]
) {
import {
addRecords(file: $file, rows: $rows) {
name
action
status
}
}
} |
Variables
Code Block |
---|
{
"file": {
"extension": "csv",
"contents": "<<BASE64 ENCODED STRING>>"
}
} |
Response
Code Block |
---|
{
"data": {
"import": {
"addRecords": {
"name": "20190404-579",
"action": "IMPORT",
"status": "queued",
"records": []
}
}
}
} |
Search batches
This is an example of searching for a batch by name.
Query
Code Block |
---|
query ImportSearch(
$filters: BatchFiltersInput
) {
import {
batches(
filters: $filters
) {
items {
name
action
status
}
pagination {
offset
limit
total
}
}
}
} |
Variables
Code Block |
---|
{
"filters": {
"name": {
"equalTo": "Test"
}
}
} |
Response
Code Block |
---|
{
"data": {
"import": {
"batches": {
"items": [
{
"name": "Test",
"action": "VALIDATE",
"status": "empty"
}
],
"pagination": {
"offset": 0,
"limit": 20,
"total": 1
}
}
}
}
} |
PayLink
To use this service we need to configure your iDEAL bank credentials and setup a landing page. Please contact us if you would like to use this service.
Status codes
Name
Description
ready
PayLink is created in our service.
started
Transaction has been started.
partially_paid
A part of the original PayLink amount is paid.
paid
The complete PayLink amount is paid.
cancelled
The last transaction of the PayLink has been cancelled.
failed
The last transaction of the PayLink has failed.
Examples
To make your start easier we have added some examples of common actions.
Keep in mind to use the POST method on all your request.
Create PayLink
Query
When using GraphQL you have the ability to define what fields you get in the response. For this example we only want the id of the created PayLink and the URLs.
Code Block |
---|
mutation createPayLink($payLink: PayLinkInput!){
payLink {
create (payLink: $payLink) {
id
shortUrl
longUrl
}
}
} |
Variables
This is the minimal information we need to create a PayLink.
Code Block |
---|
{
"payLink": {
"personName": "Alphacomm",
"invoiceAmount": "15497",
"invoiceCurrency": "EUR",
"invoiceDescription": "Example",
"invoiceReference": "103482",
"invoiceDate": "2019-02-12T10:00:00+00:00"
}
} |