Sage API Error Codes

User Navigation

What is an API?

API is an abbreviation for Application Programming Interface. It refers to a collection of standards and programming instructions that allow access to web-based software and enables different platforms to interact with one another. The API interface allows software applications to interact effectively without the need for human intervention.

What are Different API Error Codes?

A) API Error Codes related to Data Integration

SL NO	HTTP Status code	Message
1	400	//Uploading a file failed because no filename found in parameters
		{“missingParam”: {“message”: “Missing required request parameters filename”}}
2	401	//Access token is missing or expired
		{“message”: “Unauthorised”}
3	401	//Upload a file failed because filename in parameters already existed
		{“fileExists”: {“message”: “File already exists”}}
4	500	//Delete a file from the download folder failed with server error
		{“message”: “error message text”}
5	500	//Get a download link or list of files failed with server error
		{“internalError”: {“message”: “An internal error occurred”}}

Read Also-: Sage Exchange Error Codes

B) API Error Codes related to Authorization

SL NO	HTTP Status Code	Message
1	400	//a required parameter is missing
		{ message: “Missing required request parameters” }
2	400	//grant_type has another value as “authorization_code” or “refresh_token”
		{ message: “Invalid grant type” }
3	403	//Disabled app
		{ message: “The application registered on Sage Business Cloud is disabled” }
4	403	//the authorization request is still waiting for an approval of the customer
		{ message: “The pairing request has not been accepted.” }
5	403	//the expired date of the authorization request has expired
		{ message: “The request has expired.” }
6	403	//there is no authorization request related to the code provided
		{ message: “Pairing request not found” }
7	404	//No entreprise management configuration has been found with code provided
		{ message: “Could not associate the requested url with an customer application registered on Sage Business Cloud” }
8	404	//There is no application corresponding to the client_id provided
		{ message: “Could not associate the values with an active application registered on Sage Business Cloud” }
9	404	//There is no application corresponding to the redirect_uri provided or the grant_type is not “refresh_token”
		{ message: “Could not associate the values with an application registered on Sage Business Cloud” }
10	501	//unknown error
		{ message: “An internal error occurred: “ + err }
11	501	//no existing key for the encryption used in the token lambda
		{ message: “There is no existing key” }
12	501	//error during a pairing request deletion
		{ message: “Error while deleting the pairing request” }
13	501	//error during a refresh token storage
		{ message: “Error while storing refresh token” }

We hope that the discussion above has given you a good understanding of the various types of Sage API Error Codes. If you have any questions about them, we recommend that you consult with some knowledgeable Sage professionals.

Accounting Professionals & Specialized Experts

Want quick help from accounting software experts? Get in touch with our team members who can install, configure and configure your software for you. Proficient in fixing technical issues, they can help you quickly get back to work whenever you encounter an error in Sage software. Our team is available 24/7 365 days to assist you. To get in touch.

+1800-964-3096

chat with experts

💠FAQs💠

I am getting the Sage .NET API Error message “An Error has occurred in a CRM DOT NET(.NET) customization. Please Contact your Vendor to resolve”. How can I resolve this?

Let us assume that you have installed the Sage CRM v7.1 in the D drive on your computer. Then, perform the steps below to manually register the Sage CRM .NET DLLs.
🔹 Login to the Sage CRM server with the help of your Administrator account.
🔹 Run the command prompt
🔹 Browse to the path i.e. D:\Program Files\Sage\CRM\CRMDotNet\7.1\. It will include the dll files named SageCRMNet.dll and SageCRMWrapper.dll for that version.
🔹 Now, to register SageCRMNet.dll , run the command. Make sure to enter the correct name and file path, which should be D:\Program Files\Sage\CRM\CRMDotNet\7.1> regasm SageCRMNet.dll in our case
🔹 After the registration, a message will appear to inform you that the registration was successful
🔹 Next, install the DLL into the GAC or Global Assembly cache. To do this, execute the following command, D:\Program Files\Sage\CRM\CRMDotNet\7.1> gacutil -i SageCRMNet.dll
🔹 After successful registration, a message will pop up saying, “Assembly successfully added to the cache”.
🔹 Repeat the steps above to register the SageCRMWrapper.dll and install into GAC.
🔹 Finally, run the IISREST command.

How to Resolve the Sage 300 Web API Internal Server Error

This is one of the most common error messages encountered by Sage 300 web API users. The occurrence of this means the server experienced an unexpected condition and this is preventing it from executing the request sent.
Please take a note of the points below to fix this issue:
🔹 Verify your authorized user rights, which must be full in order to execute the same.
🔹 Please make sure to type the authorized user details in upper case, in the Basic authentication window.
🔹 If you need to perform the “POST” operation through the Sage 300 WEB API, you will have to send a header parameter named “Content-Type”, in addition to the default value of “application/json”.

What are the Reasons behind the Issue of Frequent Crashes while Executing a ‘Post’ Command through the Web API.?

Some of the important reasons behind this issue are:
🔹 An Avalara issue related to the Web API
🔹 An issue related to ODBC admin
🔹 Internal Server Error with Sage 300 Web API
🔹 An issue with the order entry