POST attributes that alter behaviour but are not part of resource

Along with posting back the resource to an endpoint, we also need to post back some additional parameters that control the server logic (for example to suppress sending an automated email). Should these be put in meta or is there a better approach?

I think meta could be suitable, but have never used it because my framework doesn’t support it. Instead, I generally use query parameters or headers, which is easier to implement in my case.


Thanks @cmeeren - I’ve taken your advice. Using meta is working well for us.