<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Question Re: Channel Advisor Integration in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/channel-advisor-integration/qaa-p/807403#M251785</link>
    <description>&lt;P&gt;Hi,&lt;BR /&gt;Channel Advisor supports SOAP and REST API calls, they have their own core API standards, you can send the data to then using SOAP / REST based adapter.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;The main challenge will be to include the API credentials in the API call. You can do a look up to get the token / use a constant API key provided by your partner. Though there are differences in using SOAP and REST API also they have their own pros and cons. But you will get all the structure and schema details from your Channel Advisor partner. For REST you probably have to use a OAuth token to integrate and that can be fetched using a REST lookup.&lt;/P&gt;&lt;P&gt;&lt;A href="https://developer.channeladvisor.com/rest-api-core-concepts/rest-api-vs-soap-api-benefits-drawbacks" target="test_blank"&gt;https://developer.channeladvisor.com/rest-api-core-concepts/rest-api-vs-soap-api-benefits-drawbacks&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Sample example of data structure and schema - &lt;/P&gt;&lt;P&gt;&lt;A href="https://developer.channeladvisor.com/soap-api-documentation/order-services/fulfillment-service" target="test_blank"&gt;https://developer.channeladvisor.com/soap-api-documentation/order-services/fulfillment-service&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Sugata&lt;/P&gt;</description>
    <pubDate>Fri, 01 Feb 2019 19:48:14 GMT</pubDate>
    <dc:creator>sugata_bagchi2</dc:creator>
    <dc:date>2019-02-01T19:48:14Z</dc:date>
    <item>
      <title>Channel Advisor Integration</title>
      <link>https://community.sap.com/t5/technology-q-a/channel-advisor-integration/qaq-p/807402</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;
  &lt;P&gt;My requirement is to integrate Channel Advisor(CA) with SAPPO and we need to create orders and get the shipment updates and its a standard integration OOTB provided by CA.&lt;/P&gt;
  &lt;P&gt;Link: &lt;A href="https://developer.channeladvisor.com/" target="test_blank"&gt;https://developer.channeladvisor.com/&lt;/A&gt;&lt;/P&gt;
  &lt;P&gt;Pl. suggest us how to proceed on such kind of integration.&lt;/P&gt;
  &lt;P&gt;Let us know if you need any additional information.&lt;/P&gt;</description>
      <pubDate>Fri, 01 Feb 2019 16:48:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/channel-advisor-integration/qaq-p/807402</guid>
      <dc:creator>former_member204904</dc:creator>
      <dc:date>2019-02-01T16:48:30Z</dc:date>
    </item>
    <item>
      <title>Re: Channel Advisor Integration</title>
      <link>https://community.sap.com/t5/technology-q-a/channel-advisor-integration/qaa-p/807403#M251785</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;Channel Advisor supports SOAP and REST API calls, they have their own core API standards, you can send the data to then using SOAP / REST based adapter.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;The main challenge will be to include the API credentials in the API call. You can do a look up to get the token / use a constant API key provided by your partner. Though there are differences in using SOAP and REST API also they have their own pros and cons. But you will get all the structure and schema details from your Channel Advisor partner. For REST you probably have to use a OAuth token to integrate and that can be fetched using a REST lookup.&lt;/P&gt;&lt;P&gt;&lt;A href="https://developer.channeladvisor.com/rest-api-core-concepts/rest-api-vs-soap-api-benefits-drawbacks" target="test_blank"&gt;https://developer.channeladvisor.com/rest-api-core-concepts/rest-api-vs-soap-api-benefits-drawbacks&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Sample example of data structure and schema - &lt;/P&gt;&lt;P&gt;&lt;A href="https://developer.channeladvisor.com/soap-api-documentation/order-services/fulfillment-service" target="test_blank"&gt;https://developer.channeladvisor.com/soap-api-documentation/order-services/fulfillment-service&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Sugata&lt;/P&gt;</description>
      <pubDate>Fri, 01 Feb 2019 19:48:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/channel-advisor-integration/qaa-p/807403#M251785</guid>
      <dc:creator>sugata_bagchi2</dc:creator>
      <dc:date>2019-02-01T19:48:14Z</dc:date>
    </item>
    <item>
      <title>Re: Channel Advisor Integration</title>
      <link>https://community.sap.com/t5/technology-q-a/channel-advisor-integration/qaa-p/807404#M251786</link>
      <description>&lt;P&gt;Hi Sugata, &lt;/P&gt;&lt;P&gt;Thanks for your reply. &lt;/P&gt;&lt;P&gt;We are trying to work with REST API services and the challenge here is to get the access_token using SAP PO. I have tried to configure the OAUTH 2.0 token from PO, but I am always getting error as (error: 302 found). could you pl. guide me to get the token in PO.&lt;/P&gt;&lt;P&gt;For reference we have provided with developer console to generate the token in Channel Advisor (attached token for reference)&lt;/P&gt;&lt;P&gt;Developer console: &lt;A href="https://api.channeladvisor.com/DeveloperConsole/" target="test_blank"&gt;https://api.channeladvisor.com/DeveloperConsole/&lt;/A&gt; &lt;/P&gt;&lt;P&gt;Developer Key: e391155e-20d3-4289-8aaf-00493c1fbc3e&lt;/P&gt;&lt;P&gt;&lt;A href="https://answers.sap.com/storage/attachments/273442-access-token.png"&gt;access-token.png&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards&lt;/P&gt;&lt;P&gt;Madhu&lt;/P&gt;</description>
      <pubDate>Mon, 04 Feb 2019 16:09:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/channel-advisor-integration/qaa-p/807404#M251786</guid>
      <dc:creator>former_member204904</dc:creator>
      <dc:date>2019-02-04T16:09:51Z</dc:date>
    </item>
  </channel>
</rss>

