SRTeamraiserAPI processeRegistration No Longer Working

Hello All,


Our current system uses the processRegistration method of SRTeamraiser API to create new registrations for Teamraiser events. While testing some changes to our process, the processRegistration method appeared to stop working without explanation.


Until now any errors we would get were generally of the nature that there was missing or incorrect data (e.g. 'missing required field' or 'fundraising goal must be greater than fundraising goal for participation type', and occasionally that the event was closed to registration ('event does not exist or is not available').


Now every call to processRegistration results in {"errorResponse":{"code":"1","message":"Unable to process request."}}, which according to Luminate Online API Documentation "generally indicates that an exception occurred within the internals of executing the API". I'm at a loss to explain why all of a sudden the internals of processRegistration would consistently be throwing exceptions.


Here are the details of the API call:


POST https://secure2.convio.net/*****/site/SRTeamraiserAPI?method=processRegistration&v=1.0&response_format=json&api_key=*****&login_name=*****&login_password=*****&fr_id=*****&source=&sub_source=&registration_document={XML Registration Document} HTTP/1.1

Content-Type: application/x-www-form-urlencoded

User-Agent: PostmanRuntime/7.15.2

Accept: */*

Cache-Control: no-cache

Postman-Token: {GUID}

Host: secure2.convio.net

Cookie: JSESSIONID={the session id coookie}

Accept-Encoding: gzip, deflate

Content-Length: 5509

Connection: close



Here is the response:


HTTP/1.1 403 403

Date: Mon, 26 Aug 2019 20:17:29 GMT

Server: Apache

Cache-Control: private

Content-Security-Policy: frame-ancestors 'self' *.facebook.com *.salesforce.com *.convio.net *.google.com *.force.com facebook.com salesforce.com convio.net google.com force.com; report-uri http://grusb.convio.net/site/XFrameViolation

Content-Length: 70

Keep-Alive: timeout=15, max=53

Connection: Keep-Alive

Content-Type: text/plain;charset=UTF-8


{"errorResponse":{"code":"1","message":"Unable to process request."}}


The results are the same whether the Registration Document (and 'source' and 'sub_source') is sent in the body of the POST request or as a query string parameter. Did processRegistration suddenly stop working, or am I missing something?


Any insight would be appreciated!