Help
The questions directors actually ask — a develop that failed, tokens running out mid-season, a face that drifted, a refund. Answered from the code, with the numbers checked.
Ten pages, written from the things that actually go wrong in a season. Every number on them was read out of the code that charges you, not remembered.
If the answer is not here, ask the desk — the chat in the corner of the studio. Say you want a person and one opens for you; the ticket carries your plan, your token balance and your last develop already attached, so nobody has to ask you to describe your own account. The Help item at the foot of the rail opens the same desk, and a written form if you would rather type it out.
When a develop goes wrong
- A develop failed — what happened to my tokens
- The model's face changed between frames
- A packshot came back wrong
Tokens and money
- What a look actually costs
- Running out of tokens mid-season
- Rollover, expiry, and which tokens go first
- Refunds, and what a refund does to tokens
Getting in, and letting people in
- Invitations and invitation codes
- Seats, roles, and who can spend
- API keys, and letting an agent into the house
The reference pages are next door
These pages answer "something went wrong". For how a surface works — the Lookbook, Packshots, Models, quality and cost — read the docs proper.
Webhooks
3 Webhooks routes on the FLAM API: List the house's endpoints; Register an endpoint FLAM should call; Remove an endpoint.
A develop failed — what happened to my tokens
Nothing. Tokens are held before a develop and only spent when a frame lands. A failure closes the hold and the balance returns — and a run that half-worked charges for the half that worked.