Get a recurring donation

This GET operation retrieves a recurring donation. If successful, you receive an HTTP response code of 200 and a JSON response containing the recurring donation information.

See HTTP response codes for other response codes.

GET /sqs/api/recurringDonations/<id>

HEADER INFO

authorisation: HTTP Basic Auth

tenant: <tenantName>

content-type: application/JSON

accept: application/JSON

By default, accept is XML. You must explicitly set accept in your header to application/JSON to receive a JSON response.

permissions: SQS_RECURRING_DONATION_READ_PERMISSION


URL parameters

Parameter Description

id

The auto-assigned identifier that was given to the recurring donation upon creation.


JSON response

The JSON response includes the information about the recurring donation including the donorId and groupId.

See recurring donation data type descriptions for more details on the fields in the JSON request and response. 
{
    "id": "E5B412",
    "donorId": "0871234567",
    "donorPlanId": 11224455,
    "groupId": "ABC123",
    "created": "2019-08-07T15:01:58.000+0000",
    "updated": "2019-08-07T15:01:58.000+0000"
}

SQS recurring donations data type descriptions

Field Type Description

id

string

The auto-assigned ID given to the recurring donation upon creation.

donorId

string

The MSISDN of the donor subscriber.

The subscriber’s MSISDN in international format.

donorPlanId

integer

The ID of the donor’s shareable plan.

groupId

string

The unique ID of the group. Group IDs are auto-assigned upon creation.

created

string

The date and time at which the group was created.

This is in ISO 8601 standard format.

updated

string

The date and time at which the group was updated.

This is in ISO 8601 standard format.

HTTP response codes

Code Description

200

success!

207

Multistatus response

Check out HTTP statuses for more details.
This is not applicable to all operations.

400

malformed request

401

unauthorised; bad username or password

403

forbidden; user does not have appropriate privileges

404

recurring donation not found

409

conflict with target resource

This often occurs if the item already exists, such as a plan, group, or name.
This is not applicable to all operations.

412

failed validation; this typically means that a property was not set or a value is out of range.

example
HTTP 412
{
  "errors" : [
        {
          "field" : "name",
          "description" : "name is mandatory"
        }
    ]
}

422

failed processing (after passing validation).

example
HTTP 422
{
    "message": "Subscriber max plan count exceeded",
    "errorCode": 1
}
Example 1. SQS response codes

  • 0 = no error

  • 1 = undefined general error

  • 2 = group owner/name pair is not unique

  • 3 = group owner cannot be a member

  • 4 = total member quota exceeds 100%

  • 5 = group does not exist

  • 6 = maximum group size exceeded

  • 7 = the donor does not exist

  • 8 = the shareable plan does not exist

  • 9 = the shareable plan is not a recurring plan

  • 10 = charging group owner unsupported

  • 11 = the recurring donation for this plan already exists

  • 12 = the recipient does not exist

  • 13 = the donor plan max recipient limit was exceeded

  • 14 = subscriber not found

  • 15 = quota is unavailable

  • 16 = donor plan is not shareable

500

internal error

503

request rejected due to overload