Let's look at how your application can communicate with the SuperOffice web services after authenticating and obtaining the system user ticket. You have to establish a secure connection before you start exchanging data.
In contrast to the interactive workflow, where the Authorization header uses "Bearer [access_token]", the non-interactive workflow requires the Authorization header to use SOTicket instead of Bearer, followed by the ticket value.
The ApplicationToken header must also be specified as SO-AppToken with the client secret (application token) value provided when the application was registered.
- Authorization: SOTicket System_User_Ticket_Value
- SO-AppToken: Application_Token_Value
GET /Cust26759/api/v1/MDOList/category?flat=True HTTP/1.1
authorization: SOTICKET 7T:MAA3AGYAMQBlAGQAZAAxAGQAZQAwADgAYgAxAGEAYwBkADYAOAA0ADcAMQA2ADkAOQBhADQAZgBiADMAOQAyADsAMgAwADgANwAzADEANQAwADQAMwA7AEMAdQBzAHQAMgA2ADcANQA5AA==