Message consultation happen via a HTTP GET through all the methods that start with
/ebox defined in the e-Box RESTful API.
This specification is available in the
So a Document Consumer can not only consult his messages but also reference data.
/publishMessage method is available only for Document Sender and Document Provider.
Getting an Oauth Token for consultation
The oauth introspect example shows how an Oauth token can be retrieved.
You have to request your AccessToken to the Authorization Server.
GetAccessTokenV3.getAccessToken() method is the one responsible of getting the token.
|OAuth Authorization Server URL (ACC)||https://services-acpt.socialsecurity.be/REST/oauth/v3/token|
|OAuth Authorization Server URL (PRD)||https://services.socialsecurity.be/REST/oauth/v3/token|
Getting a token requires having cleared the OAuth part of the onboarding. If it is not done yet, see the Document Consumer onboarding process.
You will get the scopes:
scope:document:management:consult:ws-eboxrestentreprise:summaryowneboxto get the summary of your e-Box;
scope:document:management:consult:ws-eboxrestentreprise:messagesfullto get and perform authorized actions on all messages in your e-Box;
scope:document:management:consult:ws-eboxrestentreprise:referencedatato retrieve the details of the messageTypes, senderOrganizations, and senderApplications.
scope:documentmanagement:ebox:enterprise:federation-rest:registryto get the list of Document Providers
Once you have got your token, you can find the list of Document Providers to call in the result of a GET request to the Provider Registry:
|Environment||URL Provider Registry|
Among them, you can find our Document Provider:
|Environment||Endpoint e-Box enterprise|
- The counters you get in the summary of your e-Box (that you can get with a GET on /ebox resource) take also into account the message set to not visible.
- If you request to get a reference data, the lists messageTypeIds, senderOrganizationIds and senderApplicationIds in response will be empty.