linkfish

Thanks a lot for all the feedback! 1. Yes will think about it. For just the API it would make definitely sense. However because the same technology currently also powers the bookmarking service which has to support as much as possible does the API also. 2. Exactly what RussianCow said. Honestly not a big fan of it either but that was the best I could come up with to accommodate that.

About the product.

1. It logs all requests which had issues with the more descriptive cause. Always go through all of them and fix the issues. The more people use it the more stuff breakes and the product can be improved. So I guess will get way better in the next days ;-) 2. Will also check and fix. 3. Will definitely look into that!

If you run into more issues or have more comments would love to hear them here or at api@link.fish . Thanks again!

Thanks, dito!

Is actually already supported when a special parameter is set(on the API-Test-Box on the landing page it is not set).

About the pricing. Was a longer process. Mainly involved what other similar services charge and much more important a price which makes the service viable in the long term.

As not native english speaker I am always happy to get help in that regard ;-) Thanks!

Thanks a lot! Will investigate and fix. If you run into any other issues please keep them coming!

It did actually just extract the data of the "hero" item. The thing is that it gets offered by multiple companies for different prices. So all the prices are valid and none is right or wrong. So really depends what you want. If you want simply "a" price, you can take the first. If you want the cheapest one you would have to itterate over them to find it.

It uses a combination of everything to extract information incl. custom parsers. The data returned to the user is always in schema.org.

Yes is similar to it in the regard that with both tools data from websites can be extracted.

Yes right now not. However an endpoint for exactly that is actually planned. So you can simply write to api@link.fish and we can inform you when it is ready.

Hard to say and compare in what regard exactly? Price wise, much cheaper. Data wise, it depends. Mainly on in what kind of data you are interested in. Will probably return better results on text-heavy pages, but the data is probably often less "deep". So really depends on the use case. If you have a question to your use case, you can simply write to api@link.fish .

Very sorry for that! Worked everywhere but should not have used a relative link on the free account signup page. Got fixed.