# Retrieve marketing flow settings `GET /api/v1/marketing-flow-settings` The store's flow sending policy. A store that has never saved one reads the DEFAULTS rather than a 404, because those defaults really are what the engine is running under; updated_at is NULL in that state, and that null is what the first PUT must send back as expected_updated_at. THE TWO HOURS ARE A SEND WINDOW, NOT A QUIET PERIOD. Sending is PERMITTED while the recipient's local hour is in [send_window_start_hour, send_window_end_hour) and deferred otherwise, so the policy "quiet hours 21:00 to 09:00" is the window [9, 21), which is the default. Reading it backwards is the single likeliest way to mail a merchant's whole list at 3am. updated_at is ALSO THE VERSION TOKEN. Send it back as expected_updated_at on the PUT, or null if this store has never saved, and your write refuses rather than reverting a change you never saw. ## Responses - `200` — Success - `400` — The request was refused before any state changed. `code` is one of: `invalid_body`, a write body this route will not take. `reason` partitions it and `field` names the key when one key is at fault. `invalid_query`, a query parameter, including limit and after. `invalid_text`, a NUL byte or bytes that are not valid UTF-8 anywhere in the path, the query or the body. Strip control characters before sending. `idempotency_key_required`, a write sent without the Idempotency-Key header. `invalid_request`, an Idempotency-Key longer than 255 bytes. Routes add their own codes for rules only they know. Switch with a default arm. - `401` — No credential, or one this API does not accept. `code` is always `unauthorized`. THE BODY IS DELIBERATELY UNINFORMATIVE. An expired key, a revoked key, a publishable key, a key belonging to another merchant and a key that never existed are all refused with the same bytes, so this response cannot be used to probe which keys exist. Check the key's state in the dashboard rather than inferring it here. Send the key as `Authorization: Bearer ` or as `X-API-Key: `. It is never accepted in a query string. - `403` — The key lacks the read_marketing_flows scope. `code` is `insufficient_scope` and the message names the scope to ask the merchant for. - `429` — Too many requests. `code` is `rate_limited`. Two limits apply independently: one on the credential and the route family, one on the client address. The headers describe whichever has less left, so honouring Retry-After always clears the window that bound. - `default` — Any status this operation does not list, in the same envelope. A 5xx means the request may or may not have applied. Retry it with the SAME Idempotency-Key: that is the only way to find out without risking a duplicate, and it is what the key is for. A few 4xx conditions arrive here rather than as a listed status because they depend on the merchant's plan or on a module being wired: 402 when a quota or a plan limit is reached, and 503 when a capability the route needs is not configured on this deployment. Both carry a `code` naming which. ## Example ```bash curl --request GET \ --url 'https://api.mercemur.com/api/v1/marketing-flow-settings' \ --header 'Authorization: Bearer ' ```