Skip to main content

Assets Server REST API - error handling


Do you have corrections or additional information about this article? Leave a comment!
Do you have a question about what is described in this article? Please contact Support.


  • Tim Strehle

    I think it would be helpful to document the recently-added returnStatusOkOnErrorForServicesApi cluster property on this page:

    # Historically, the Assets Server REST API under /services/* returned 200 OK on
    # error to enable legacy browsers to connect across cross-domain. URLs outside
    # /services will return non-200 status codes in case of errors.
    # The following settings are supported:
    # true   = return 200 OK on error, with JSON errorcode in the body.
    # false  = return non-200 status codes (4xx, 5xx), with same JSON errorcode
    #          in the body.
    # 403    = only return 403 status code, but return 200 OK for errorcodes
    #          other than 403 (403 reported for CSRF errors).
    # This setting only affects APIs under /services/*
  • Maarten van Kleinwee

    Hi Tim,

    Thank you for the feedback. I passed it on to the developers and it turns out that the sendServiceErrorAsJson option described in this article has actually been deprecated and cannot be used anymore. I have added a note to this article to point this out and to refer to the returnStatusOkOnErrorForServicesApi option.

    Best regards,

    Maarten van Kleinwee
    Senior Technical Writer, WoodWing Software 


Please sign in to leave a comment.