[SalesForce] Is it possible to have multiple POST calls in the same Apex REST class

I have a requirement to write a REST class to fetch different set of resources that need to be accessed through different endpoints.
Eg.

/services/apexrest/abc/contractors
/services/apexrest/abc/departments

Both the calls have to be POST calls as we need to send some details in request body. I read some QnA articles mentioning there can be only one @HttpPost method per class. (https://developer.salesforce.com/forums/?id=906F00000009DiDIAU)

But is there any alternate way to write a single apex class that can handle multiple POST calls ?

Best Answer

You're free to write your resource as:

@RestResource(urlMapping='/abc/*')

Where * indicates a wildcard; this will match any resource that matches this wildcard pattern.

From here, you can then dispatch various methods:

@HttpPost global static void doPost() {
  switch on RestContext.request.requestURI.substringAfterLast('/')) {
    when 'contractors' { doContractorPost(); }
    when 'departments' { doDepartmentsPost(); }
    when else { doInvalidCall(); }
  }
}

What you do from here is up to you. It's just code.

Related Solutions

[SalesForce] HttpCalloutMock Interface where there is more than 1 callout

Salesforce passes in the HTTPRequest made by the logic your testing into the mock implementation to help with this type of requirement. So in the HttpCalloutMock.respond method implementation. You can call req.getBody() and condition the response based on that, here is an example...

@IsTest
private with sharing class MultiHttpMockTest 
{
    public class MockHttpResponseGenerator implements HttpCalloutMock
    {
        public HTTPResponse respond(HTTPRequest req) 
        {   
            HttpResponse res = new HttpResponse();
            res.setHeader('Content-Type', 'text/xml');
            if(req.getBody().contains('Call 1'))
                res.setBody('<soapenv:Envelope><soapenv:Body>Response 1</soapenv:Body></soapenv:Envelope>');
            else if(req.getBody().contains('Call 2'))
                res.setBody('<soapenv:Envelope><soapenv:Body>Response 2</soapenv:Body></soapenv:Envelope>');
            else if(req.getBody().contains('Call 3'))
                res.setBody('<soapenv:Envelope><soapenv:Body>Response 3</soapenv:Body></soapenv:Envelope>');            
            res.setStatusCode(200);
            return res;
        }
    }

    public static testmethod void testMultiMockResponse()
    {
        // Set single mock implementation that responds dynamically to different requests
        Test.setMock(HttpCalloutMock.class, new MockHttpResponseGenerator());

        // Frst request
        Http h = new Http();        
        HttpRequest req1 = new HttpRequest();
        req1.setEndpoint('http://mygreatservice.com/foo/bar');
        req1.setMethod('POST');
        req1.setBody('<soapenv:Envelope><soapenv:Body>Call 1</soapenv:Body></soapenv:Envelope>');
        HttpResponse res1 = h.send(req1);
        System.assertEquals('<soapenv:Envelope><soapenv:Body>Response 1</soapenv:Body></soapenv:Envelope>', res1.getBody());

        // Second request       
        HttpRequest req2 = new HttpRequest();
        req2.setEndpoint('http://mygreatservice.com/foo/bar');
        req2.setMethod('POST');
        req2.setBody('<soapenv:Envelope><soapenv:Body>Call 2</soapenv:Body></soapenv:Envelope>');
        HttpResponse res2 = h.send(req2);
        System.assertEquals('<soapenv:Envelope><soapenv:Body>Response 2</soapenv:Body></soapenv:Envelope>', res2.getBody());

        // Third request        
        HttpRequest req3 = new HttpRequest();
        req3.setEndpoint('http://mygreatservice.com/foo/bar');
        req3.setMethod('POST');
        req3.setBody('<soapenv:Envelope><soapenv:Body>Call 3</soapenv:Body></soapenv:Envelope>');
        HttpResponse res3 = h.send(req3);
        System.assertEquals('<soapenv:Envelope><soapenv:Body>Response 3</soapenv:Body></soapenv:Envelope>', res3.getBody());                    
    }
}

[SalesForce] REST API calls to 3rd Party (Pardot), multiple @future callouts

The reason why @future returns void is because it's asynchronous. It doesn't start until the calling code's transaction has finished. There's no way to communicate back to the calling code at all. Odds are, you'll want to make createProspectsByLead a @future method instead, so you can authenticate and then perform your action. You can have 100 calls per transaction (as of Winter '15 release), so it's unlikely you'll need more than just a couple of calls. And you should definitely cache the API key so you don't waste calls (if applicable), and perform more efficiently anyways.

For handling the response, see Dom.Document for reading an XML file. A successful load would probably reduce the complexity to:

Dom.Document d = new Dom.Document();
d.load(res.getBody());
String api_key = d.getRootElement().getChildElement('rsp',null).getChildElement('api_key', null).getText();

Best Answer

Related Solutions

[SalesForce] HttpCalloutMock Interface where there is more than 1 callout

[SalesForce] REST API calls to 3rd Party (Pardot), multiple @future callouts

Related Topic