Skip to content

Conversation

@joshwanf
Copy link
Collaborator

Resolves #250 by adding validation/serialization to the relevant endpoints. Invalid requests return a standardized ApiError with a message. For the case where someone creates a Screener while supplying a publishedScreenerId field, the API responds with:

{
  error: true;
  message: "Unknown field 'publishedScreenerId'";
}

ApiError can be used elsewhere to return a response instead of throwing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Screener API Security

2 participants