A place in the traveller's journal
Approved partners publish listings — an itinerary, a room, a service — and travellers meet them inside the same app they are already using to record what they saw.
WildJournal Business
Partner with WildJournal
WildJournal is a field journal for people who travel to see wildlife. Their sightings stay on their own phone — we never ask a traveller where they were. What we do put in front of them is the people who make the trip happen: you.
Already approved? Sign in with your partner token.
What WildJournal Business is
One account you control
A single partner token signs you in. Your profile and every listing under it are yours to write, edit, publish, unpublish and archive whenever you like, without asking us.
A separate product, deliberately
This is the business side of WildJournal and nothing else. There is no journal here and no traveller data: a partner account can see what that partner publishes, and nothing more.
Four ways to partner
Itinerary planner
You design the trip — the days, the parks, the pacing. Publish itineraries travellers can follow inside the app, day by day, with each day marked confirmed or pending as you lock it in.
- Publishes itinerary listings
- Day-by-day trips in the traveller's journal
- Your name and note on every trip you plan
Booking agent
You turn a plan into a booking — permits, vehicles, guides, seats. List the packages you can actually fulfil and the seasons you cover, so travellers reach you when they are ready to commit.
- Publishes service listings
- From-price and duration stated up front
- Enquiries routed to your listed contact
Hotelier
You host them at the end of a long day. Publish your rooms — board, pricing, what a stay is actually like — described by the town or region the property sits in.
- Publishes room listings
- Described by town or region name
- Seasonal availability in your own words
Other services
Naturalist guides, photography workshops, transfers, equipment hire, conservation programmes. If it makes a wildlife trip better, list it — tell us what you do and we will place it properly.
- Publishes service listings
- Reviewed individually before publishing
- Room to describe something we haven't seen yet
Not a commercial operator? Reserves, forest departments, NGOs, universities, research institutes, foundations, safari operators, eco-lodges and photography companies apply through the same form, and publish events, expeditions and guide or expert profiles instead.
How it works
- Apply. Ten minutes, no account needed. You get an application ID.
- We review. A person reads it. You can check the status any time with that ID.
- You get a token. On approval we issue one partner token, shown once.
- You publish. Sign in with the token, complete your profile, create listings.
The arrangement, in plain words
- Applying
- No account, no token, no software. Fill in the form, keep the application ID it gives you, and check back with it whenever you want.
- Review
- A person reads every application, and we reply to every one — including the ones we decline. If something needs clarifying we write to the contact you gave us.
- Your token
- Approval issues exactly one partner token, shown once. It is a secret, like a password: it signs you in, and it is the only thing that does. Lose it and we will issue a new one — we cannot show you the old one again.
- Your listings
- A new listing starts as a private draft. You decide when it goes live, you can take it back to draft at any time, and archiving keeps it while hiding it from travellers. Nothing is published on your behalf.
- What we set, not you
- Your partner type and your account standing are ours. If an account stops trading its listings are hidden and editing is disabled until an operator reactivates it — your token keeps working throughout, so there is nothing for you to replace.
What we will never ask you for
No coordinates, no map pins, no street addresses — not from travellers, and not from you. Partners and listings are described by town or region name, as free text. This is enforced by the server itself: a request carrying a location-like field is rejected before it reaches any handler, and an application answer that looks like a postal address is refused with an explanation.