<p>Those are called Enterprise addresses, originally intended for exchanges but everyday users have started to adopt them for various reasons. Unfortunately, I can't speak to why Blockfrost API chokes when it encounters one, but there are other APIs that support these. Try Koios for example.</p>
<p><a href="https://api.koios.rest/#get-/address_assets" rel="nofollow noreferrer">https://api.koios.rest/#get-/address_assets</a></p>
<p>EDIT: Ah! Just noticed an important part of your message.. The reason you're getting the timeout error is because enterprise addresses do not have stake addresses as they were never meant to stake (again they are intended for exchanges). That's why this is timing out.</p>

CC BY-SA 4.0
2022-03-04T09:01:13.807Z
Wow, thanks for the great answer !! That makes perfect sense. Do you have any specific way to spot those addresses (length of the address?)
Lokinou
CC BY-SA 4.0
2022-03-04T12:15:12.563Z
Yes, length of address would be a great way to go. As far as I know the enterprise addresses are all the same length. The reason they are shorter is because they lack the stake key hash.
Tygar Pool
CC BY-SA 4.0
2022-03-04T02:31:23.993Z
2022-03-04T02:31:23.993Z
Tygar Pool
<p>Using blockfrost I have pulled a list of addresses of owners of a specific fungible token.
Some of the addresses are significantly smaller than the others (about  2/3 the length).</p>
<p>When querying blockfrost for stake keys (or pool.pm) with those addresses i get an error 504 after a long timeout, while all the others work smoothly.</p>
<p>An example of the syntax and function used with python is the following <code>api.address(addr_str)</code></p>
<p>Here is the address causing me trouble <code>addr1w999n67e86jn6xal07pzxtrmqynspgx0fwmcmpua4wc6yzsxpljz3</code></p>
<p>How should I handle those, what are they?</p>

<address><blockfrost>
Short address crashed blockfrost calls
# Short address crashed blockfrost calls

(Asked by: username_0 on 2022-03-04)

Using blockfrost I have pulled a list of addresses of owners of a specific fungible token.
Some of the addresses are significantly smaller than the others (about 2/3 the length).

When querying blockfrost for stake keys (or pool.pm) with those addresses i get an error 504 after a long timeout, while all the others work smoothly.

An example of the syntax and function used with python is the following `api.address(addr_str)`

Here is the address causing me trouble `addr1w999n67e86jn6xal07pzxtrmqynspgx0fwmcmpua4wc6yzsxpljz3`

How should I handle those, what are they?

**Tags:** address, blockfrost

---

## 1 answers

### Answer by username_1 on 2022-03-04. Score: 4

Those are called Enterprise addresses, originally intended for exchanges but everyday users have started to adopt them for various reasons. Unfortunately, I can't speak to why Blockfrost API chokes when it encounters one, but there are other APIs that support these. Try Koios for example.

<https://api.koios.rest/#get-/address_assets>

EDIT: Ah! Just noticed an important part of your message.. The reason you're getting the timeout error is because enterprise addresses do not have stake addresses as they were never meant to stake (again they are intended for exchanges). That's why this is timing out.

> **Comments:**
> **username_0**: Wow, thanks for the great answer !! That makes perfect sense. Do you have any specific way to spot those addresses (length of the address?)  
> **username_1**: Yes, length of address would be a great way to go. As far as I know the enterprise addresses are all the same length. The reason they are shorter is because they lack the stake key hash.  

---

