What is the difference between HTTP 404 and HTTP 500 status codes in Appian integrations?

When an Appian integration object calls an external REST API, the HTTP status code tells you whether the request succeeded or failed. A 404 and a 500 point to different kinds of problems.

404 Not Found

The server can’t find the requested resource or endpoint. Common causes:

1. The API URL or endpoint is wrong.
2. The resource doesn’t exist, was deleted, or was moved.
3. The HTTP method or routing configuration is wrong.
4. In some APIs, access permissions are missing.

For example, if Appian calls GET /api/customers/999 and customer 999 doesn’t exist, the API may return a 404.

To troubleshoot, verify the URL and HTTP method, check that the resource exists, and validate the request parameters and permissions.

500 Internal Server Error

The server hit an unexpected problem while processing the request. Common causes:

1. Unhandled exceptions in backend code.
2. Database connection failures.
3. Server configuration issues.
4. Errors in backend business logic.
5. Failures in dependent services.

For example, if Appian calls GET /api/customers/123, the endpoint exists, but the backend can’t connect to its database and returns a 500.

To troubleshoot, read the response body for error details, review the backend logs, check database connectivity and dependent services, and involve the API team if needed.

How Appian handles these errors

By default, an integration object treats HTTP error responses such as 404 and 500 as integration failures. The response exposes three fields:

1. success tells you whether the integration succeeded.
2. result.statusCode holds the HTTP status code, when available.
3. error.message holds the integration error message.

Sample Screenshot How Appan shows the status codes

You can configure custom error handling in the integration object so users see meaningful messages.

If you’re calling an Appian Web API, a 404 can also mean the caller lacks Web API permissions, and a 500 can mean the Web API expression failed to evaluate.

Interview answer

Say that a 404 usually points to a resource or endpoint problem, and a 500 to a server-side processing problem. Then add that you’d inspect the response and logs before naming a root cause.

Offical Appain Docs Ref:

https://docs.appian.com/suite/help/26.9/Integration_Tutorial.html