API

[K.S. DeVille]

  Dear LMFDB Team,

I was wondering whether the API being down is a known issue and whether it might be back up again soonish?

Thank you!  

[David Lowry-Duda]

Dear K.S.,

The LMFDB API seems ok on my end. For example, the call

https://www.lmfdb.org/api/ec_curvedata/?_format=json&torsion_structure=li2;2&_delim=;&_offset=0

responds as expected. What are you seeing that's going wrong?

- DLD

[Andrew Sutherland]

The API has been disabled a few times in the past few weeks while we were dealing with some unruly bots that were ignoring robots.txt and putting an excessive load on our servers,. It should be working now, but if you make too many queries in too short a period of time your IP may get blocked, or you may be redirected to a captcha page (if you are accessing the API in an automated way, you may need to throttle your requests in order to avoid this).

If you encounter further problems please let us know and provide some more details about what you are trying to do and what is not working.

[John Jones]

I am not sure these responses went to the original person, so cc'ing.

John

--
You received this message because you are subscribed to the Google Groups "lmfdb-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lmfdb-suppor...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/lmfdb-support/a09ed5d2-0571-411f-9f0c-826baa57f54bn%40googlegroups.com.

[John Cremona]

Kris, in case it is helpful the elliptic curve data you need is also
available in text files at https://github.com/JohnCremona/ecdata with
a front page at https://johncremona.github.io/ecdata/. The majority
of the data in the LMFDB's elliptic curve tables is there.

John Cremona

On Fri, 22 Aug 2025 at 16:06, John Jones <j...@asu.edu> wrote:
>
>
>
> ---------- Forwarded message ---------
> From: K.S. DeVille <krist...@gmail.com>
> Date: Fri, Aug 22, 2025 at 6:54 AM
> Subject: Re: API
> To: John Jones <j...@asu.edu>
>
>
> Hey, thanks for getting back in touch.
>
> The website I was given for the api was incorrect, apologies. I’m helping a colleague crunch some entropy analyses on your elliptic‐curve database, and we’ve run into download issues (reCAPTCHA blocks, FTP hiccups, etc.). Could you please point me to a reliable way to pull the entire “ec_curvedata” dump in one go?
>
> Specifically, we’d love access to the JSON-lines file that contains, for each curve: label, rank, conductor, torsion_order and aplist (the Frobenius trace list)
>
> If there’s an HTTPS URL (or S3 bucket, rsync mirror, etc.) for curvedata.json.gz (or a CSV equivalent), that would be ideal.
>
> Thanks so much for your help- my machine is much faster than my colleague’s, so I’m happy to mirror and redistribute locally once I have the bulk file.
>
> Best, Kris
>
> (I can send this to the original email if you prefer?)

> To view this discussion, visit https://groups.google.com/d/msgid/lmfdb-support/CAJciYuQn7erQ8fZ%2BKORGwxohoo2UyNytRE63%3DkWPSVLZu7RjQA%40mail.gmail.com.

[Edgar Costa]

Here are several options to get data from lmfdb: https://www.lmfdb.org/api/options

And here is the ec_curvedata table for your convenience: https://math.mit.edu/~edgarc/files/ec_curvedata.txt

I will remove the file by the end of the month.

On Fri, Aug 22, 2025 at 11:06 AM John Jones <j...@asu.edu> wrote:

---------- Forwarded message ---------
From: K.S. DeVille <krist...@gmail.com>
Date: Fri, Aug 22, 2025 at 6:54 AM
Subject: Re: API
To: John Jones <j...@asu.edu>

Hey, thanks for getting back in touch.

The website I was given for the api was incorrect, apologies. I’m helping a colleague crunch some entropy analyses on your elliptic‐curve database, and we’ve run into download issues (reCAPTCHA blocks, FTP hiccups, etc.). Could you please point me to a reliable way to pull the entire “ec_curvedata” dump in one go?

Specifically, we’d love access to the JSON-lines file that contains, for each curve: label, rank, conductor, torsion_order and aplist (the Frobenius trace list)

If there’s an HTTPS URL (or S3 bucket, rsync mirror, etc.) for curvedata.json.gz (or a CSV equivalent), that would be ideal.

Thanks so much for your help- my machine is much faster than my colleague’s, so I’m happy to mirror and redistribute locally once I have the bulk file.

Best, Kris

(I can send this to the original email if you prefer?)

On Fri, 22 Aug 2025 at 01:57, John Jones <j...@asu.edu> wrote:

To view this discussion, visit https://groups.google.com/d/msgid/lmfdb-support/CAJciYuQn7erQ8fZ%2BKORGwxohoo2UyNytRE63%3DkWPSVLZu7RjQA%40mail.gmail.com.