oanor
Sign up free
Marketplace Pricing Features Sign in

API · /fishing-api

Fishing Tackle API

healthy 3,588 Subscribers

Angling and tackle maths as an API, computed locally and deterministically — the three numbers that decide how a reel is spooled and a lure is fished. The line-capacity endpoint works out how much line of a different diameter a reel will hold: line lies on the spool by cross-sectional area, so capacity scales with the inverse square of diameter — a reel rated for 100 yards of 0.30 mm holds about 73.5 yards of thicker 0.35 mm, or nearly 140 yards of a thinner 0.011-inch braid. The sink-time endpoint gives the countdown to fish a lure at depth: time = depth ÷ sink rate, so a minnow that sinks a foot a second reaches ten feet on a count of ten. The drag endpoint sets the reel: about 25–33 % of the line's breaking strength measured at the rod tip — a 20-pound line wants roughly 5 to 6.6 pounds of drag, enough to let a fish run before anything snaps. Everything is computed locally and deterministically, so it is instant and private. Ideal for fishing and tackle apps, reel-spooling and gear-shop tools, angler trip-planners, and learning sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Unit-agnostic — keep your units consistent; rules of thumb, conditions vary.

#fishing #angling #tackle #reel #outdoor #developer-tools
api.oanor.com/fishing-api
Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

/api/fishing-api/openapi.json
/api/fishing-api/llms.txt

Discovery: GET /api/index.json lists every API.

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
93 ms
Server probes · 24h
Subscribers
3,588
active
Total calls
4
last 7 days
status Full status page → · 8 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 4,500 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • 4,500 calls/month
  • 2 req/sec
  • Line capacity + sink time + drag
  • No credit card
Sign in to subscribe

Starter

€3.75 /month

  • 70,000 calls / month
  • 8 requests / second
  • Hard cap (429 above quota, no overage)
  • 70,000 calls/month
  • 8 req/sec
  • Any line & unit
  • Email support
Sign in to subscribe

Pro

€12.10 /month

  • 300,000 calls / month
  • 20 requests / second
  • Hard cap (429 above quota, no overage)
  • 300,000 calls/month
  • 20 req/sec
  • Tackle-shop & app pipelines
  • Priority support
Sign in to subscribe

Mega

€36.80 /month

  • 1,400,000 calls / month
  • 48 requests / second
  • Hard cap (429 above quota, no overage)
  • 1,400,000 calls/month
  • 48 req/sec
  • Platform scale
  • Dedicated SLA
Sign in to subscribe

Built by

P
PremiumApi

Related APIs

Other APIs with overlapping tags.

Climbing Fall API

Rock-climbing fall maths as an API, computed locally and deterministically — the safety numbers behind a lead fall, from the harshness of the catch to whether you hit the deck. The fall-factor endpoint gives the fall factor, distance fallen ÷ rope paid out, from 0 to a maximum of 2: it, not the absolute distance, decides how hard the catch is, so 4 metres on 2 metres of rope is a brutal factor-2 onto the anchor while the same fall on 10 metres of rope is a mild 0.4. The impact-force endpoint gives the peak force the rope transmits from the spring model F = mg + √((mg)² + 2·mg·k·f), where k is the rope modulus (~20 kN for a dynamic single rope) and f the fall factor — so an 80 kg climber on a factor-1 fall feels about 6.4 kN, and the top runner sees roughly 1.66× that from the pulley effect. The ground-fall endpoint adds it up: total drop = twice the height above the last piece, plus slack, plus the rope's stretch, and tells you whether that clears the ground or a ledge. Everything is computed locally and deterministically, so it is instant and private. Ideal for climbing apps, gym and guiding tools, route-planning and education sites, and gear calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Educational estimates — not a substitute for instruction and judgement.

api.oanor.com/climbing-api

Hammock Hang API

Hammock-hang maths as an API, computed locally and deterministically — the suspension-force, ridgeline and strap-height numbers a camper or hammock hanger sets up by. It all comes back to the 30-degree rule. The force endpoint shows why: the tension in each suspension line is the occupant weight ÷ (2 × sin of the hang angle), so at a 30° hang each strap carries about one body weight, but flatten the hang to 15° and it jumps to roughly 1.9 times — which is what over-stresses straps, trees and your back when people pull a hammock drum-tight. The ridgeline endpoint sizes a structural ridgeline at about 83 % of the hammock length, the fixed line that reproduces that ~30° lay and the right sag on any pair of trees. The strapheight endpoint estimates how high to attach the straps from the distance between the trees and the seat height you want, since trees farther apart need higher anchor points to hold the angle. Everything is computed locally and deterministically, so it is instant and private. Ideal for camping, backpacking, outdoor-gear and hammock app developers, hang-calculator and trip-planning tools, and adventure software. Pure local computation — no key, no third-party service, instant. Weight and lengths in your own unit. Live, nothing stored. 3 compute endpoints.

api.oanor.com/hammock-api

Climbing Grade API

Rock-climbing grade conversion as an API, computed locally and deterministically — the cross-system grade translations a climber, gym or guidebook app needs when the same route reads differently in every country. The route endpoint takes a roped-climbing grade in any major system — the American Yosemite Decimal System (5.5 to 5.15d), French sport grades (4b to 9c+), the UIAA scale used across Central Europe (IV to XIII-) or the Australian/New Zealand Ewbank numbers (12 to 40) — and returns the equivalents in all of them, so a 5.11a is a French 6c, a UIAA VII+ and an Ewbank 22. The boulder endpoint converts between the American V-scale (VB and V0 to V17) and the French Fontainebleau scale (3 to 9A), so a V5 is Font 6C and a problem graded 7A is about V6. You can pass a grade in any supported system and it finds the row and gives the rest — handy for syncing a tick list across regions or showing a climber a grade they recognise. Everything is computed locally and deterministically, so it is instant and private. Ideal for climbing, bouldering, gym, guidebook and outdoor-sports app developers, tick-list and route-database tools, and training-log software. Pure local computation — no key, no third-party service, instant. Chart equivalents — grades are inherently approximate across systems. Live, nothing stored. 2 conversion endpoints.

api.oanor.com/climbgrade-api

Archery & Arrow API

Archery and arrow maths as an API, computed locally and deterministically — the FOC, energy and arrow-weight numbers an archer or bowhunter tunes a setup with. The FOC endpoint finds the front-of-center balance, the share of an arrow’s weight that sits forward of the middle: FOC = ((balance point − length ÷ 2) ÷ length) × 100 measured from the throat of the nock, so a 28-inch arrow balancing at 16 inches is 7.1 % — and it bands the result, since target archers run about 7–12 % while hunters push 12–19 % for penetration and forgiveness. The energy endpoint turns arrow weight and speed into terminal performance: kinetic energy (ft-lb) = grains × fps² ÷ 450,240 and momentum (slug-fps) = grains × fps ÷ 225,218, so a 400-grain arrow at 280 fps carries about 69.7 ft-lb and 0.50 slug-fps, with a suggested game class — momentum, not KE, is the better penetration predictor for heavy arrows. The weight endpoint totals a finished arrow from its parts — shaft (grains-per-inch × length) plus point, insert, nock and fletching — and divides by draw weight for grains-per-pound, flagging the 5-GPP minimum that protects the bow. Everything is computed locally and deterministically, so it is instant and private. Ideal for archery, bowhunting, traditional-archery and outdoor-sports app developers, arrow-builder and bow-tuning tools, and pro-shop calculators. Pure local computation — no key, no third-party service, instant. Imperial archery units. Live, nothing stored. 3 compute endpoints. For sight marks or bow tuning use a different API.

api.oanor.com/archery-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for Fishing Tackle API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call Fishing Tackle API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for Fishing Tackle API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does Fishing Tackle API cost?
Fishing Tackle API has a free tier with 100 calls / month. Paid plans start at €3.75 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is Fishing Tackle API GDPR-compliant?
All requests to Fishing Tackle API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.

Pick an endpoint from the list on the left to see its details and try it.

Code snippets

Sign up to get an API key, then call any path under your slug.

curl https://api.oanor.com/fishing-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/fishing-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/fishing-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
    "https://api.oanor.com/fishing-api/SOME_PATH",
    headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())

Ratings

Sign in to rate.

No reviews yet.

Discussion

Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.

Sign in to start a thread or reply.

Sign in

New thread

/ 4000

📌 Pinned 🔒 Locked

·

· ·

/ 4000

🔒 This thread is locked — no new replies.

  • No threads yet — start the discussion.

Support

Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.

Sign in to open a support ticket.

Sign in

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

  • No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.