Integrating iPaper on client's website

[ghimpresa...@gmail.com]

Hello there, I'm interested in implementing Scribd document viewer on
my client's website. It is suposed to be done by linking directly
documents on our server. I found out that these documents are being
converted into iPaper format and than uploaded on Scribd servers. I
have few question regarding embedding the viewer on other websites.

1.) Can I set documents to "private status" automaticaly?
I do not want that these docs are to be found or/and viewed on Scibd
using public search (because of some legal issues). In fact, I would
prefer to have possibility to convert documents to iPaper and host
them directly on my server, not to be forced to upload them to Scribd.
Is this possible?

2.) What happens if Scribd changes some standards?
Will I be informed on time about future changes and on what should I
do to reintegrate them on my website?

3.) Is the "disable more documents" feature enabled in the API?

4.) I have tried to contact through the QPP form but there was no
response. Is it only US based?


thanks for your attention
best
Harun

[Jared Friedman]

Hi Harun,
That's great that you'll be implementing iPaper on your client's
website. Send us a link when the integration is done so we can check
it out.

> 1.) Can I set documents to "private status" automaticaly?
> I do not want that these docs are to be found or/and viewed on Scibd
> using public search (because of some legal issues). In fact, I would
> prefer to have possibility to convert documents to iPaper and host
> them directly on my server, not to be forced to upload them to Scribd.
> Is this possible?

Yes, you can set documents to private automatically. In the
docs.upload or docs.uploadFromUrl method where you upload the
documents to Scribd, you can specify the privacy. See the
documentation for details.

> 2.) What happens if Scribd changes some standards?
> Will I be informed on time about future changes and on what should I
> do to reintegrate them on my website?

Our expectation is that all changes will be backwards-compatible and
will not break existing applications.

> 3.) Is the "disable more documents" feature enabled in the API?

Not yet, but it will be in the very near future.

> 4.) I have tried to contact through the QPP form but there was no
> response. Is it only US based?

No, I am not sure what happened. Try again and make sure the form goes through?

Best,
Jared