1. If the type is a special error, then the description could be also more concrete.
2. This special 400 error shouldn't have a Generic400 as example

I'm not completely getting the special error comment. Since in CAMARA we are using examples to include specific errors, I chose to create a different schema containing both examples. So this way we have two schemas, one containing only Generic 400 for the endpoints that doesn't have subscriptionId and another one containing both.

Is there a better way to do it without adding it inline? or do you mean that it should only have the specific error because the Generic doesn't apply?

What description do you think would be more appropriate?

I thought that since we also have the Generic400 error, then this SubscriptionIdRequired is a specialized one, so it could have a

• description like "SubscriptionId is missing" and

• it should only have one example, exactly this case when subscriptionid is missing:

      examples:
            status: 400
            code: INVALID_ARGUMENT
            message: "Expected property is missing: subscriptionId"
  

As discussed in the meeting we remove the missing suscriptionId example. It would make sense to maintain it if the error code was different, but since it is still INVALID ARGUMENT, we can skip it.