Packing and licensing an API


I've started and launched a small SaaS application. It offers a simple API that allows developers to create and manage passes for Apple's Passbook.

Part of the offering is an implementation of the Apple defined API that passes use to register themselves and to fetch updates. It isn't a very difficult API to implement, but the storage and management of the data behind it is reasonably complex.

I've had two developers ask about licensing this component of my application as they would rather host it themselves, rather than pay the fees I would charge. Whilst this isn't ideal, I'd rather get something for my efforts.

As my service is new, they are concerned that it may stop be available in the future. To offset the risk, they would like to integrate my code into their solutions.

I am willing to license my code to them, but I'm unsure how to place a value on the source code.

Would anyone be able to offer me advice on how to proceed with licensing the code?

Software Licensing

asked Aug 24 '13 at 17:47
114 points
  • Your question is unclear, but it sounds like you are asking for technical advice, which is not within the scope of this site. – Zuly Gonzalez 7 years ago
  • Are you asking about the money side ("place a value on the source code") or the legal side (how to actually structure a license to allow this without giving up too much of it)? – rbwhitaker 7 years ago
  • Also what do you mean by 'API' - are you asking how you'd go about licencing Apples API? Or are you talking about your implementation of it (ie. your code library)? – Steve 7 years ago
  • Thanks for the edit. However, your question is still unclear. It's hard to figure out what you're actually asking. Please edit to clarify your question. Asking "how to license software" is too broad. – Zuly Gonzalez 7 years ago

Your Answer

  • Bold
  • Italic
  • • Bullets
  • 1. Numbers
  • Quote
Not the answer you're looking for? Ask your own question or browse other questions in these topics:

Software Licensing